Skip to content

Conversation

@apricote
Copy link
Member

@apricote apricote commented Jul 8, 2024

It was theoretically possible to get into ugly situations if these resources were not installed in the right order. As kubernetes usually reconciles the state, the clusters would eventually work as expected, but getting it right on the first try is way faster.

It was theoretically possible to get into ugly situations if these
resources were not installed in the right order. As kubernetes usually
reconciles the state, the clusters would eventually work as expected,
but getting it right on the first try is way faster.
@apricote apricote added the bug Something isn't working label Jul 8, 2024
@apricote apricote self-assigned this Jul 8, 2024
@apricote apricote requested a review from a team as a code owner July 8, 2024 08:46
@apricote apricote merged commit 28e1878 into main Jul 8, 2024
@apricote apricote deleted the explicit-deps branch July 8, 2024 08:56
apricote pushed a commit that referenced this pull request Jul 8, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.5.1](v0.5.0...v0.5.1)
(2024-07-08)


### Bug Fixes

* broken cluster if resources are installed in wrong order
([#25](#25))
([28e1878](28e1878))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants