| --- | |
| kind: ClusterRole | |
| apiVersion: rbac.authorization.k8s.io/v1 | |
| metadata: | |
| name: kindnet | |
| rules: | |
| - apiGroups: | |
| - "" | |
| resources: | |
| - nodes |
It may be required for some applications to be aware of the cluster domain.
This information is not exposed directly, the cluster domain is a kubelet property, https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/
--cluster-domain string
However, if you set the subdomain field in a Pod, then you are able to access the FQDN directly from the Pod
kubectl apply -f backend.yaml
kubectl get service
| package main | |
| import ( | |
| "fmt" | |
| "log" | |
| "os" | |
| "github.com/google/nftables" | |
| ) |
Useful for troubleshooing network namespaces problems without having to create containers and the additional functionality
source netns.sh
netns_add ns1 192.168.0.2
netns_add ns2 192.168.0.3
ping -c 2 192.168.0.2
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
cat <<EOF | kind create cluster --config=-
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
Conformance test are a subset of the e2e test Kubernetes test.
The e2e tests are based on Ginkgo https://onsi.github.io/ginkgo/ and live in the Kubernetes repository https://github.com/kubernetes/kubernetes/tree/master/test/e2e.
There is no guarantee of compatibility for the e2e binaries, hence the e2e binary version MUST match your kubernetes cluster version.
| - ./kubernetes/typed/certificates/v1.CertificateSigningRequestInterface.Apply: added | |
| - ./kubernetes/typed/certificates/v1.CertificateSigningRequestInterface.ApplyStatus: added | |
| - ./kubernetes/typed/rbac/v1.ClusterRoleBindingInterface.Apply: added | |
| - ./kubernetes/typed/rbac/v1.ClusterRoleInterface.Apply: added | |
| - ./kubernetes/typed/rbac/v1.RoleBindingInterface.Apply: added | |
| - ./kubernetes/typed/rbac/v1.RoleInterface.Apply: added | |
| - ./kubernetes/typed/apiserverinternal/v1alpha1.StorageVersionInterface.Apply: added | |
| - ./kubernetes/typed/apiserverinternal/v1alpha1.StorageVersionInterface.ApplyStatus: added | |
| - ./informers/storage/v1beta1.Interface.CSIStorageCapacities: added | |
| - ./informers/policy.Interface.V1: added |
| #!/bin/bash | |
| set -xe | |
| # This script takes as a parameter the name of the VM | |
| # and creates a linked clone | |
| # Ref: https://unix.stackexchange.com/a/33584 | |
| # The scripts assumes that it runs from the same folder | |
| # where the vm image is located and it coincides with the | |
| # image name |
KIND runs Kubernetes cluster in Docker, and leverages Docker networking for all the network features: port mapping, IPv6, containers connectivity, etc.
KIND uses a docker user defined network.
It creates a bridge named kind