Skip to content
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

Make OpenSLO spec concrete #294

Merged
merged 2 commits into from
Oct 10, 2024
Merged

Make OpenSLO spec concrete #294

merged 2 commits into from
Oct 10, 2024

Conversation

fpiwowarczyk
Copy link
Member

Problem statement

We claim that OpenSLO should be vendor agnostic, this means that spec should be running for different vendors without any additional changes. At least to the core, vendor specific annotations should be fine. With this bullet point there is possibility that the same spec won't work for two vendors although both of them clam that they support OpenSLO and they are right.

Another thing is that recently we decided that we want to make OpenSLO not only easy to use but also easy to implement as we want new projects to start using this spec. Taking specification concrete and simple is step into this direction.

@fourstepper
Copy link
Collaborator

fourstepper commented Oct 9, 2024

I would like to change this in the v1 as well. Doesn't break spec nor implementation (as discussed on the OpenSLO meeting)

@fpiwowarczyk
Copy link
Member Author

@fourstepper yup, this PR is about v1.

@fourstepper fourstepper merged commit 2f77393 into main Oct 10, 2024
1 check passed
@fourstepper fourstepper deleted the remove-expanded-name branch October 10, 2024 09:22
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