![]() The following example shows how to use in-line patches to change the podinfo deployment.Īdd the following to the field spec of your podinfo-kustomization. To customize a deployment from a repository you don’t control, you can use Flux To resume updates run the command flux resume kustomization. To suspend updates for a kustomization, run the command flux suspend kustomization. Suspending updates to a kustomization allows you to directly edit objects applied from a kustomization, without your changes being reverted by the state in Git. When you alter the podinfo deployment using kubectl edit, the changes are reverted to match When you delete a Kustomization from the fleet-infra repository, Flux removes all Kubernetes objects previously applied from that Kustomization. When a Kubernetes manifest is removed from the podinfo repository, Flux removes it from your cluster. Kubernetes manifests in the master branch are reflected in your cluster. NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE The output is similar to: NAME READY UP-TO-DATE AVAILABLE AGE Kubectl -n default get deployments,services Configures Flux components to track the path /clusters/my-cluster/ in the repository.Ĭlone the fleet-infra repository to your local machine:.Deploys Flux Components to your Kubernetes Cluster.Adds Flux component manifests to the repository.Creates a git repository fleet-infra on your GitHub account.The bootstrap command above does the following: ► installing components in flux-system namespaceĭeployment "source-controller" successfully rolled outĭeployment "kustomize-controller" successfully rolled outĭeployment "helm-controller" successfully rolled outĭeployment "notification-controller" successfully rolled out The output is similar to: ► connecting to ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |