Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

shipperctl: split "shipperctl admin clusters apply" #358

Merged
merged 1 commit into from
Oct 12, 2020

Conversation

hihilla
Copy link
Contributor

@hihilla hihilla commented Oct 8, 2020

This is a cherry-pick of #292

First of all, this does away with the "admin" namespace. Commands were getting too long for our taste.

Second, shipperctl admin clusters apply is now split into two,
supposed to be called in order, like so:

shipperctl clusters setup management
shipperctl clusters join -f clusters.yaml

The first only installs Shipper in the management cluster, and the
second joins application clusters to the management one. This allows us
to roll out updates to shipper without necessarily having to specify
application clusters to be joined.

First of all, this does away with the "admin" namespace. Commands were
getting too long for our taste.

Second, `shipperctl admin clusters apply` is now split into two,
supposed to be called in order, like so:

```
shipperctl clusters setup management
shipperctl clusters join -f clusters.yaml
```

The first only installs Shipper in the management cluster, and the
second joins application clusters to the management one. This allows us
to roll out updates to shipper without necessarily having to specify
application clusters to be joined.
@hihilla hihilla merged commit a0e7d64 into master Oct 12, 2020
@hihilla hihilla deleted the hilla/cherry-pick-292 branch October 12, 2020 14:10
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants