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

Procedure to deploy registry HA #3400

Merged
merged 6 commits into from
Jun 2, 2021
Merged

Conversation

TeddyAndrieux
Copy link
Collaborator

@TeddyAndrieux TeddyAndrieux commented May 27, 2021

Component:

'salt', 'docs', 'tests'

Context:

The first step of bootstrap HA (registry + repository HA)

Summary:

  • Update the salt module to retrieve Kubernetes endpoint to retrieve the full list of all endpoints and not only a single one.
  • Configure contained and repo with all repositories endpoints (HA registry and repo)
  • Add tests for registry
  • Add procedure to deploy registry container on a second node (HA registry)

See: #2002

@TeddyAndrieux TeddyAndrieux requested a review from a team May 27, 2021 08:59
@bert-e
Copy link
Contributor

bert-e commented May 27, 2021

Hello teddyandrieux,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented May 27, 2021

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@TeddyAndrieux TeddyAndrieux force-pushed the improvement/repository-ha branch 11 times, most recently from 61e6b0e to b7c62e4 Compare May 28, 2021 15:14
@TeddyAndrieux TeddyAndrieux marked this pull request as ready for review May 28, 2021 16:59
Copy link
Contributor

@alexandre-allard alexandre-allard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First round, wording/typos/etc. :)

docs/operation/registry_ha.rst Outdated Show resolved Hide resolved
docs/operation/registry_ha.rst Outdated Show resolved Hide resolved
docs/operation/registry_ha.rst Outdated Show resolved Hide resolved
docs/operation/registry_ha.rst Outdated Show resolved Hide resolved
docs/operation/registry_ha.rst Outdated Show resolved Hide resolved
docs/operation/registry_ha.rst Outdated Show resolved Hide resolved
docs/operation/registry_ha.rst Outdated Show resolved Hide resolved
docs/operation/registry_ha.rst Outdated Show resolved Hide resolved
docs/operation/registry_ha.rst Outdated Show resolved Hide resolved
Copy link
Contributor

@alexandre-allard alexandre-allard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

tests/post/steps/test_registry.py Show resolved Hide resolved
salt/metalk8s/repo/redhat.sls Outdated Show resolved Hide resolved
Update the salt module to retrieve Kubernetes endpoint to retrieve the
full list of all endpoints and not only a single one.
Update the containerd and repository configuration to support multi
endpoint
We may want to configure ISO on differents nodes for registry HA so make
sure we have all needed dependencies on all minions
If we try to import a solution where repositories container is not yet
deployed, the "expose" state will fail as expected directory does not
exists yet. But in case of HA registry we want to run the
`solutions.available` state before actual creating the repository
container
Add a simple test for registry HA when running on multi node cluster

root@bootstrap $ kubectl exec -n kube-system -c salt-master \\
--kubeconfig=/etc/kubernetes/admin.conf \\
salt-master-bootstrap -- salt '*' state.sls \\
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This pod name is not fixed, so this isn't a copy-paste command, even though it looks like one. This needs to be explained.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree, but it's not only here, everywhere in the documentation we do this ... which is an issue I agree

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a bug, cc @thomasdanan

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will replace this one at least

salt/_pillar/metalk8s_endpoints.py Show resolved Hide resolved
@bert-e
Copy link
Contributor

bert-e commented Jun 2, 2021

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following reviewers are expecting changes from the author, or must review again:

The following options are set: approve

@NicolasT NicolasT dismissed their stale review June 2, 2021 15:05

Comment handled

@bert-e
Copy link
Contributor

bert-e commented Jun 2, 2021

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

@TeddyAndrieux
Copy link
Collaborator Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Jun 2, 2021

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/2.10

The following branches will NOT be impacted:

  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Jun 2, 2021

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/2.10

The following branches have NOT changed:

  • development/2.0
  • development/2.1
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

Please check the status of the associated issue None.

Goodbye teddyandrieux.

@bert-e bert-e merged commit 6808653 into development/2.10 Jun 2, 2021
@bert-e bert-e deleted the improvement/repository-ha branch June 2, 2021 17:26
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.

None yet

4 participants