Cloud provider static manifests¶
A cloud provider static manifest refers to the specific infrastructure configuration files required for Kubernetes controllers to function correctly in different hosting environments.^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]
These manifests ensure that the appropriate networking and routing rules are applied, whether the cluster is running on a local environment like Docker Desktop or a public cloud platform.^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]
Implementation¶
In the context of the NGINX Ingress Controller, static manifests are applied via kubectl using a URL that points to the specific provider's configuration.^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]
For example, the following command retrieves and applies the static manifest specifically designed for generic cloud providers:^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]
[kubectl](<./kubectl.md>) apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/controller-v1.3.1/deploy/static/provider/cloud/deploy.yaml
Alternatively, if the source file is available locally, it can be applied directly:^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]
[kubectl](<./kubectl.md>) apply -f ./deploy.yaml
Related Concepts¶
- Kubernetes
- Ingress Controller
- [[Docker Desktop]]
Sources¶
^[400-devops-06-kubernetes-k8s-ingress-controller-docker-desktop-readme.md]