Replies: 3 comments 2 replies
-
You should get multiple different checks, one for each Kustomization. If you have multiple different clusters that all have Kustomizations by the same name, you might see this issue. Is that the case for your configuration? For alerts that surface through a notification provider like Slack, you get a "summary" field which is meant to let you specify which cluster is impacted by the change. For commit status notifications, I don't think this field has any effect (but you can try it also!) |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Not sure when it happened, but noticed that we are now getting a different id per commit status Is it possible to configure the id to make it more human readable? |
Beta Was this translation helpful? Give feedback.
-
We have a multi env setup using single branch model on gitlab.
We have configured git commit status ref https://fluxcd.io/flux/components/notification/provider/#git-commit-status
The problem we are facing is that each env will override each others commit status.
If we could set the
context
on the gitlab commit status API ref https://docs.github.com/en/rest/commits/statuses#create-a-commit-statusWe could differentiate the status of each env on the same commit
Beta Was this translation helpful? Give feedback.
All reactions