ingress
kubectl-aliases
Our great sponsors
ingress | kubectl-aliases | |
---|---|---|
3 | 7 | |
13,202 | 3,259 | |
- | - | |
9.7 | 3.1 | |
over 1 year ago | 5 months ago | |
Go | Shell | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ingress
-
Expose multiple backends with multiple IPs with Kubernetes Ingress resources
I exposed a service with a static IP and an Ingress through an nginx controller as one of the examples of the kubernetes/ingress repository. I have a second LoadBalancer service, that is not managed by any Ingress resource that is no longer properly exposed after the adding the new resources for the first service (I do not understand why this is the case).
-
How to set up kubernetes NGINX ingress in AWS and SSL termination
I've deployed ingress controller from https://github.com/kubernetes/ingress/tree/master/examples/aws/nginx
-
Ingress responding with 'default backend - 404' when using GKE
I have read and tried pretty much everything that I could find, including stuff from here and here and here, but maybe I'm just missing something... any ideas?
kubectl-aliases
-
☸️ Kubernetes: A Pragmatic Kubectl Aliases Collection
# autocomplete kubectl & helm source <(kubectl completion zsh) source <(helm completion zsh) alias k=kubectl # when using below aliases, print kubectl command and then execute it function kctl() { echo "+ kubectl $@" && command kubectl $@ } # add aliases collection like 'kgpo' for 'kubectl get pods` from https://github.com/ahmetb/kubectl-aliases [ ! -f ~/.kube/aliases.sh ] && curl -fsSL "https://raw.githubusercontent.com/ahmetb/kubectl-aliases/master/.kubectl_aliases" > ~/.kube/aliases.sh && sed -i -e 's/kubectl/kctl/g' ~/.kube/aliases.sh source ~/.kube/aliases.sh # set default namespace alias kn='kctl config set-context --current --namespace' # get events sorted by last timestamp alias kgel='kctl get events --sort-by=.lastTimestamp' # get events sorted by creation timestamp alias kgec='kctl get events --sort-by=.metadata.creationTimestamp' # get pod's descending events function kger() { kctl get events --sort-by=.lastTimestamp --field-selector involvedObject.name="$@" } # get 'real' all alias kgworld='kctl get $(kubectl api-resources --verbs=list --namespaced -o name | paste -sd ",")' # display all nodes resources request and limits alias kgnr="k get nodes --no-headers | awk '{print \$1}' | xargs -I {} sh -c 'echo {} ; kubectl describe node {} | grep Allocated -A 5 | grep -ve Event -ve Allocated -ve percent -ve -- ; echo '" # start a debug pod (including lots of troubleshooting tools) alias kdebug="kctl -n default run debug-$USER --rm -it --tty --image leodotcloud/swiss-army-knife:v0.12 --image-pull-policy=IfNotPresent -- bash" # get pod's containers list function kgpc() { kctl get pod -o jsonpath="{.spec.containers[*].name}" "$@" && echo "" } # ping a service, ex: 'kping whoami:8080' alias kping='kctl run httping -it --image bretfisher/httping --image-pull-policy=IfNotPresent --rm=true --' # get existing pod's yaml without forbidden fields, ex: 'kyaml pod whoami' function kyaml() { kubectl get "$@" -o yaml | kubectl-neat } # display and delete failed pods in current namespace alias krmfailed='kctl delete pods --field-selector=status.phase=Failed'
- Good and/or helpful aliases to know for CKA/CKAD/Daily use?
-
Aliasing kubectl with "kc"
I like https://github.com/ahmetb/kubectl-aliases because it helps keep the formal nomenclature in my head while providing faster terminal entry.
- What are your aliases?
- Most important discussion from KubeCon
-
Everything Useful I Know About kubectl
I would highly recommend not aliasing k to kubectl and instead get this: https://github.com/ahmetb/kubectl-aliases
- For local projects, do you change your node port range?
What are some alternatives?
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes
kube-ps1 - Kubernetes prompt info for bash and zsh
kubernetes-ingress - NGINX and NGINX Plus Ingress Controllers for Kubernetes
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
konfig - konfig helps to merge, split or import kubeconfig files
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
ingress - WIP Caddy 2 ingress controller for Kubernetes
ingress-gce - Ingress controller for Google Cloud
kutectl - A couple of bash aliases and functions to make your life easier when dealing with kubectl.
kubectl-tmux-exec - A kubectl plugin to control multiple pods simultaneously using Tmux