![]() ![]() For example, a secret added in src/main/kubernetes/kubernetes.yml will be added to both the generated kubernetes.yml and kubernetes.json. These resources will end up in both generated formats (json and yaml). The provided file may be either in json or yaml format and may contain one or more resources. An openshift.json/ openshift.yml file added in src/main/kubernetes will only affect the generated openshift.json/ openshift.yml.Ī knative.json/ knative.yml file added in src/main/kubernetes will only affect the generated knative.json/ knative.yml and so on. So, a kubernetes.json/ kubernetes.yml file added in src/main/kubernetes will only affect the generated kubernetes.json/ kubernetes.yml. The correlation between provided and generated files is done by file name. kubernetes.json, openshift.json, knative.json, or the yml equivalents). Those resources can be added under src/main/kubernetes directory and can be named after the target environment (e.g. a ConfigMap, a Secret, a Deployment for a database) or provide custom ones that will be used as a base for the generation process. Sometimes it’s desirable to either provide additional resources (e.g. Allow Kubernetes Pods to suggest a pre-defined Parser (read more about it in Kubernetes Annotations section) Off. The older syntax is still supported but is deprecated, and it’s advised that you migrate to the new syntax. Previous versions of the Kubernetes extension supported a different syntax to add environment variables. ![]() ![]()
0 Comments
Leave a Reply. |