Space
: Switch pane from vertical align to horizontal.
persistence: | |
enabled: true | |
accessModes: | |
- ReadWriteOnce | |
size: 5Gi | |
datasources: | |
datasources.yaml: | |
apiVersion: 1 | |
datasources: |
!Home page all videos page | |
youtube.com##ytd-browse.ytd-page-manager.style-scope | |
!Suggestion by youtube | |
youtube.com###related | |
!Removes comments | |
##.ytd-comments.style-scope |
Ref:
- We have two worker nodes, able to communicate with each other.
- Each nodes have multiple pods running and each pod is able to communicate with any other pod in any other node(till node is accessible)
3 Basic requirements that kubernetes has put are:
Configure a Linux bridge interface
- In computer networking, a bridge is a network device that interconnects more than one LAN segment at Layer-2.
- This bridge functionality is built into the Linux kernel, so one can set up a software bridge interconnecting multiple network interfaces.
A Linux bridge can be created with a user-space command-line tool called brctl which allows you to create, remove and administer Linux Ethernet bridges.
In backend of all docker networking:
- When the daemon instantiates the container, it assigns a unique network address to it, connecting it to a virtual Ethernet bridge, which in the case of Docker is called docker0.
- All containers in the system communicate with each other by directing packets to docker0, which then forwards those packets through the subnet automatically.
Ref: http://www.ieee802.org/1/files/public/docs2008/new-dcb-ko-VEB-0708.pdf
- That is, 1 or more OSs share the PCI device through the VI.
- VI may be part of Hypervisor or not.
- Multiplexes flows from multiple OSs.
- Performs PCI IO transactions on behalf of the OS;
(Reference)
- https://www.digitalocean.com/community/tutorials/a-deep-dive-into-iptables-and-netfilter-architecture
- https://www.karlrupp.net/en/computer/nat_tutorial
- https://goyalankit.com/blog/iptables
- http://ipset.netfilter.org/iptables.man.html
Iptables interfaces with the kernel's netfilter packet filtering framework, it works by interacting with the packet filtering hooks, these kernel hooks are known as the netfilter framework.
AWS CLI
-
Get ec2 instance with name and private ip:
aws ec2 describe-instances --query "Reservations[*].Instances[*].[InstanceId,Tags[?Key=='Name']| [0].Value,PrivateIpAddress]" --output table
-
Get instance details in some human readable format:
aws ec2 describe-instances --query 'Reservations[*].Instances[*].{ID:InstanceId,TYPE:InstanceType,Subnet:SubnetId,VPC:VpcId,IP:PublicDnsName,State:State.Name }' --output table