-
Notifications
You must be signed in to change notification settings - Fork 21
Conversation
natmegs
commented
Jan 13, 2020
•
edited
Loading
edited
- Update kommander monitoring addon endpoints
- Update kommander UI endpoint
- Add grafana annotations to kommander addon
- Bump kommander and opsportal charts
@shaneutt can you let me know if this follows the correct contribution pattern? |
endpoint.kubeaddons.mesosphere.io/kommander-grafana: "/ops/portal/kommander/monitoring/grafana" | ||
docs.kubeaddons.mesosphere.io/thanos: "https://thanos.io/getting-started.md/" | ||
docs.kubeaddons.mesosphere.io/karma: "https://github.com/prymitive/karma" | ||
docs.kubeaddons.mesosphere.io/kommander-grafana: "https://grafana.com/docs/" |
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.
@gracedo it's kind of hard to see in the diff but all that's changed in these files are the annotations - specifically, the endpoints (changed to the /ops/portal/kommander/monitoring/x
pattern per slack), and adding annotations for kommander's grafana. Also changed the kommander UI endpoint as I think that the monitoring endpoint changes are dependent on the ui path change? Let me know if this looks right!
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.
Let's wait on this until the charts work is all done (I was planning on modifying the annotations with the kommander bump). I was told that maybe prior to GA it was okay to modify instead of create a new revision, but I'm also not entirely sure :p
@gracedo Ok - I'll label this blocked for now until the charts stuff is ready |
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.
mesosphere/charts#351 was merged so we should be unblocked now!
chartReference: | ||
chart: kommander | ||
repo: https://mesosphere.github.io/charts/stable | ||
version: 0.3.3 |
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.
Let's update this to 0.3.10 (mesosphere/charts#351)
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.
make that 0.3.13, pushed up a fix :) mesosphere/charts#356
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.
I think this should be kept as is since we're not updating the addon itself, 0.3.13
is added for 1.182.x
versions.
that said, I'm not sure if we can/need to add these annotations to 1.163.x
versions, they dont even support it, right?
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.
since we're not updating the kommander chart version here, do we need this file addons/kommander/1.163.x/kommander-2.yaml
?
chartReference: | ||
chart: kommander | ||
repo: https://mesosphere.github.io/charts/stable | ||
version: 0.3.9 |
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.
Let's update this to 0.3.10 (mesosphere/charts#351)
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.
^ 0.3.13
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.
same comment/question as above
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.
I think we should consider updating to the latest patch version as @gracedo suggested, and then ✔️
03f8105
to
f034ca1
Compare
I took I can see that maintaining that many versions will get messy kinda fast… |
chartReference: | ||
chart: kommander | ||
repo: https://mesosphere.github.io/charts/stable | ||
version: 0.3.3 |
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.
I think this should be kept as is since we're not updating the addon itself, 0.3.13
is added for 1.182.x
versions.
that said, I'm not sure if we can/need to add these annotations to 1.163.x
versions, they dont even support it, right?
chartReference: | ||
chart: kommander | ||
repo: https://mesosphere.github.io/charts/stable | ||
version: 0.3.9 |
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.
same comment/question as above
tested this PR on my cluster, its running 1.182.14 and uses |
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.
I've spoken with @juliangieseke about this in Zoom and Slack, and discussed some of the confusion related to this PR:
We are working on expanded documentation which will cover how to make releases and how to manage removing unsupported versions of an Addon which appear will be particularly helpful for Kommander which is updating rapidly and older versions are not necessarily useful to keep around.
You can track the documentation that's being created here: https://jira.mesosphere.com/browse/DCOS-62869
In the meantime, I believe we can merge this as is to get the immediate benefit of getting the patched latest revision out.
After we publish our new documentation it should be much simpler and more autonomous to do so without needing assistance from other repository code owners, @juliangieseke and I are planning on getting this fully resolved and set into motion next tuesday.
I'm going to look into the CI issues as per DCOS-62937 |
So far the CI issues appear as though they may be deficiencies in teamcity resources, as I can pass the KommanderTestGroup tests locally. I'm continuing my review. |
CI may have just been flaky, as tests are now passing. Please re-review and get this one moving through. |
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.
Hmm, karma seems to be at the old /kommander/monitoring/karma
url instead of behind /ops/portal/kommander
- blocking this to investigate further
We are going to have another chart bump shortly for kommander and I'd like to get that in here as well before it merges. |
I added a new commit to change from kommander 1.182.x to 1.184.x and to also update the opsportal chart. This is now blocked on mesosphere/charts#361 |
I think it was also blocked on mesosphere/charts#360 - I've merged that and tested this branch on my cluster. thanos & grafana are accessible on |
@gracedo can you please unblock this pr? 🙇 |
@juliangieseke just starting up a cluster now to check. or - if you still have yours up running this version, can you check |
Remove unnecessary value overrides.
91f229b
to
a8f2864
Compare
I've cleaned up this PR to match the one for 1.3.0-rc.1 branch (#84). @jimmidyson kept your commit, but its still broken |