ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
I see patchesStrategicMerge in my kustomization.yaml file, but not getting it clearly, like whats its need or why we require that? kustomization.yaml resources: - a.yaml patchesStrategicMerge: - b.yaml - c.yaml I went through this: https://kubernetes.io/docs/tasks/manage-kubernetes-objects/kustomization/#customizing and https://github.com/kubernetes/communit
Asked · Feb 17
answered · Feb 17
I've got this ingress.yaml base configuration: apiVersion: extensions/v1beta1 kind: Ingress metadata: labels: sia: aza app: asap-ingress-internal name: asap-ingress-internal annotations: kubernetes.io/ingress.class: "nginx-external" nginx.ingress.kubernetes.io/use-regex: "true" spec: rules: - host: the-host-value http: paths: - path: /asap-srv-template/(.*)
I have a kustomize base that I'd like to re-use without editing it. Unfortunately, it creates a namespace I don't want to create. I'd like to simply remove that resource from consideration when compiling the manifests and add a resource for mine since I can't patch a namespace to change the name. Can this be done? How?
Based on the docs that I've read, there are 3 methods of patching: patches patchesStrategicMerge patchesJson6902. The difference between patchesStrategicMerge and patchesJson6902 is obvious. patchesStrategicMerge requires a duplicate structure of the kubernetes resource to identify the base resource that is being patched followed by the modified portion of t
I have been using the Kubernetes and Helm for a while and have now come across Kustomize for the first time. But what exactly is the difference between Kustomize and Helm? Are both simply different solutions for bundling K8s elements such as services, deployments, ...? Or does it make sense to use both Helm and Kustomize together?
yaml
kubernetes