-
Notifications
You must be signed in to change notification settings - Fork 9
Fix default namespace installation error for tigera and custom-resource #498
New issue
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
Conversation
Pull Request Test Coverage Report for Build 17512924608Details
💛 - Coveralls |
Signed-off-by: Shiva Kumar (SW-CLOUD) <[email protected]>
3f83be8 to
74ecf48
Compare
|
/ok to test 74ecf48 |
| # based on https://docs.tigera.io/calico/latest/getting-started/kubernetes/quickstart | ||
| echo "Installing Calico ${CALICO_VERSION}..." | ||
| with_retry 3 10s kubectl --kubeconfig $KUBECONFIG create -f https://raw.githubusercontent.com/projectcalico/calico/${CALICO_VERSION}/manifests/tigera-operator.yaml | ||
| with_retry 3 10s kubectl get installation default -n tigera-operator || kubectl --kubeconfig $KUBECONFIG create -f https://raw.githubusercontent.com/projectcalico/calico/${CALICO_VERSION}/manifests/tigera-operator.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The kubectl calls should be consistent. Here you have one kubectl call using the
--kubeconfigand the other without the flag - Moreover, the
kubectl get installationcall seems unnecessary here. The creation of the installation custom resource does not happen until L138, so this change should be reverted. It is unncessary here
| # Install Calico custom resources | ||
| echo "Installing Calico custom resources..." | ||
| with_retry 3 10s kubectl --kubeconfig $KUBECONFIG create -f https://raw.githubusercontent.com/projectcalico/calico/${CALICO_VERSION}/manifests/custom-resources.yaml | ||
| with_retry 3 10s kubectl get installation default -n tigera-operator || kubectl --kubeconfig $KUBECONFIG create -f https://raw.githubusercontent.com/projectcalico/calico/${CALICO_VERSION}/manifests/custom-resources.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-
The kubectl calls should be consistent. Here you have one kubectl call using the --kubeconfig and the other without the flag
-
Also, it is always better to use the FQDN of a custom resource when referencing it in automation scripts
| with_retry 3 10s kubectl get installation default -n tigera-operator || kubectl --kubeconfig $KUBECONFIG create -f https://raw.githubusercontent.com/projectcalico/calico/${CALICO_VERSION}/manifests/custom-resources.yaml | |
| with_retry 3 10s kubectl get installations.operator.tigera.io default -n tigera-operator || kubectl --kubeconfig $KUBECONFIG create -f https://raw.githubusercontent.com/projectcalico/calico/${CALICO_VERSION}/manifests/custom-resources.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
opened new PR and testing @tariq1890 @ArangoGutierrez
#499
No description provided.