-
Notifications
You must be signed in to change notification settings - Fork 0
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
Okteto fixing #22
base: master
Are you sure you want to change the base?
Okteto fixing #22
Conversation
okteto-example.yml
Outdated
@@ -1,16 +1,9 @@ | |||
name: xcube-hub-okteto |
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.
Hi Tonio,
name: xcube-hub
I was wrong yesterday. This line should contain the name of the deployment i.e. xcube-hub
. Okteto replaces the xcube-hub pod in teh xcube-hub deployment with the okteto pod. This allows you to debug the hub within the K8s infrastructure. Nice but playing around has broken the deployment yesterday.
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.
This also has of course implications for dev. Once shoud work in the own minikube or so. Not on the dev cluster except one wants to check something specific.
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.
Nice but playing around has broken the deployment yesterday.
Well, it was already broken yesterday. I applied your suggestion, so now it should be fine.
Codecov Report
@@ Coverage Diff @@
## master #22 +/- ##
=======================================
Coverage 86.65% 86.65%
=======================================
Files 76 76
Lines 4625 4625
=======================================
Hits 4008 4008
Misses 617 617 Continue to review full report at Codecov.
|
dev cluster is working. It turned out that there were no problems with this file after all, we just needed to restart the deployment.