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

fix: Clarify the manager CLI command deploy kontrol service location argument #247

Merged
merged 3 commits into from
Sep 25, 2024

Conversation

laurentluce
Copy link
Contributor

Some users are confused about the kardinal kontrol service location argument. Some of them are not able to differentiate between the kardinal manager location and the kontrol service location. I myself was also confused when I saw the manager deploy command.

@laurentluce laurentluce merged commit 54bdc21 into main Sep 25, 2024
14 checks passed
lostbean added a commit that referenced this pull request Sep 26, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.3.0](0.2.7...0.3.0)
(2024-09-26)


### ⚠ BREAKING CHANGES

* new gateway management
([#238](#238))

### Features

* E2E tests iteration
[#2](#2)
([#237](#237))
([c4f6b67](c4f6b67))
* new gateway management
([#238](#238))
([b5a9916](b5a9916))


### Bug Fixes

* add missing resources to policy
([#249](#249))
([0ade319](0ade319))
* Clarify the manager CLI command deploy kontrol service location
argument ([#247](#247))
([54bdc21](54bdc21))
* Do not alter the istio-system namespace
([#246](#246))
([1c98304](1c98304))
* Exit with code 1 upon errors in the CLI
([#243](#243))
([63c640e](63c640e))
* Handle gateway case where the baseline is missing or not labelled
([#245](#245))
([b0b6bb2](b0b6bb2))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
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