Adding Configmap handling to deployments #1408
Annotations
2 errors and 5 warnings
|
Deploy application
YAMLException: duplicated mapping key at line 11, column 5:
app.kubernetes.io/name: testapp
^
|
|
Fail if any error
Process completed with exit code 6.
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: azure/[email protected], asdf-vm/actions/install@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, azure/[email protected], Azure/[email protected], asdf-vm/actions/install@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Deploy application
KUBECONFIG env is not explicitly set. Ensure cluster context is set by using k8s-set-context action.
|
|
Deploy application
Deployment strategy is not recognized.
|
|
Bake deployment
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Loading