Skip to content

Make config in-line with next version of Perses Operator (merge after next Perses Operator release)#94

Draft
saswatamcode wants to merge 1 commit intoperses:mainfrom
saswatamcode:operatorver
Draft

Make config in-line with next version of Perses Operator (merge after next Perses Operator release)#94
saswatamcode wants to merge 1 commit intoperses:mainfrom
saswatamcode:operatorver

Conversation

@saswatamcode
Copy link
Copy Markdown
Member

Perses Operator will have breaking changes in config in next version.
This commit brings the YAML + jsonnet up to speed with that.

cc: @jgbernalp for when next version of Perses Operator is release.

Signed-off-by: Saswata Mukherjee <saswataminsta@yahoo.com>
@saswatamcode
Copy link
Copy Markdown
Member Author

Looks like this api change wasn't in latest Perses Operator release, we'll wait till next major bump

@slashpai
Copy link
Copy Markdown
Member

I had logged #239 while working on integrating with kube-prometheus, it looks like this is related. https://github.com/perses/perses-operator/releases latest v0.3.2 is available now and we are good to proceed to migrate to v1alpha2 as well

@saswatamcode would you be continuing with this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants