We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spec: apicast: stagingSpec: customPolicies: - name: Example version: "0.1" secretRef: name: policy
spec: apicast: stagingSpec: customPolicies: - name: example version: "0.1" secretRef: name: policy
Then, the deploymnent config has two volumemounts. It is expected to have only one.
Initially, with the original CR, the deployment config looked like this:
apiVersion: apps.openshift.io/v1 kind: DeploymentConfig metadata: annotations: apps.3scale.net/apicast-policy-volume-550ce71bf15f7ab80906b5e066d2fc30: policy-01-example spec: template: spec: volumes: - name: policy-01-example secret: defaultMode: 420 secretName: policy containers: - volumeMounts: - mountPath: /opt/app-root/src/policies/Example/0.1 name: policy-01-example readOnly: true
After the CR change, it looks like this:
apiVersion: apps.openshift.io/v1 kind: DeploymentConfig metadata: annotations: apps.3scale.net/apicast-policy-volume-550ce71bf15f7ab80906b5e066d2fc30: policy-01-example spec: template: spec: volumes: - name: policy-01-example secret: defaultMode: 420 secretName: policy containers: - volumeMounts: - mountPath: /opt/app-root/src/policies/Example/0.1 name: policy-01-example readOnly: true - volumeMounts: - mountPath: /opt/app-root/src/policies/example/0.1 name: policy-01-example readOnly: true
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Steps to reproduce
Then, the deploymnent config has two volumemounts. It is expected to have only one.
Initially, with the original CR, the deployment config looked like this:
After the CR change, it looks like this:
The text was updated successfully, but these errors were encountered: