Mira's attempts to understand Kuwubernetes |
Links | RSS | |
Author | ArgentumCation | Posts | Notes |
---|---|---|---|
License | CC-BY-NC-SA 4.0+ | Updated |
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
|
|
kubectl apply -f <yaml>
to deploy a yaml fileThe above two result in the following
$ kubectl describe svc
Name: adminer
Namespace: default
Labels: io.kompose.service=adminer
Annotations: <none>
Selector: io.kompose.service=adminer
Type: ClusterIP
IP Family Policy: SingleStack
IP Families: IPv4
IP: 10.43.229.81
IPs: 10.43.229.81
Port: 8090 8090/TCP
TargetPort: 8080/TCP
Endpoints: 10.42.0.10:8080
Session Affinity: None
Internal Traffic Policy: Cluster
Events: <none>
Adminer can be accesed at 10.42.0.10:8080
[!TODO] how tf do I access this from 127.0.0.1 or outside?
kubectl expose deployment <deployment_name> --port=<port> --target-port=<target_port> --type=NodePort
kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.1/standard-install.yaml
export KUBECONFIG=/etc/rancher/k3s/k3s.yaml