Skip to content

Add upgrade warnings#19061

Merged
kisunji merged 2 commits intomainfrom
kisunji/vault-ca-upgrade
Oct 4, 2023
Merged

Add upgrade warnings#19061
kisunji merged 2 commits intomainfrom
kisunji/vault-ca-upgrade

Conversation

@kisunji
Copy link
Contributor

@kisunji kisunji commented Oct 4, 2023

Backports
1.15.x
1.14.x

@kisunji kisunji requested a review from a team as a code owner October 4, 2023 17:10
@vercel
Copy link

vercel bot commented Oct 4, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
consul ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 4, 2023 5:15pm
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
consul-ui-staging ⬜️ Ignored (Inspect) Oct 4, 2023 5:15pm

@github-actions github-actions bot added the type/docs Documentation needs to be created/updated/clarified label Oct 4, 2023
@kisunji kisunji added pr/no-changelog PR does not need a corresponding .changelog entry backport/1.14 backport/1.15 This release series is no longer active on CE. Use backport/ent/1.15. backport/1.16 This release series is no longer active on CE. Use backport/ent/1.16. labels Oct 4, 2023
Copy link
Contributor

@jkirschner-hashicorp jkirschner-hashicorp left a comment

Choose a reason for hiding this comment

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

Left some comments/questions. Overall looks good. Thanks for getting this up quickly!


#### Service mesh compatibility ((#service-mesh-compatibility-1-15))

Upgrade to **Consul version 1.15.2 or later**.
Copy link
Contributor

Choose a reason for hiding this comment

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

Do these all belong within a "service mesh compatibility" section (like exists for 1.15 and 1.14)?

And would it affect our upgrade guidance here? Like ... upgrade to Consul 1.15.2 or later, but avoid 1.15.6 if [using Vault Enterprise as a CA](link to anchor tag).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I moved around the sections so they fall under "service mesh compatibility" except for 1.16 which didn't have the section.


## Consul 1.16.x

#### Vault Enterprise as CA
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should add to KNOWN ISSUES in the changelog

The changelog content can link to the applicable upgrade guidance section in our docs (here) once published.

The changelog PR can be separate (since it won't be backported in any way).

Copy link
Contributor

@jkirschner-hashicorp jkirschner-hashicorp left a comment

Choose a reason for hiding this comment

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

LGTM.

Note that auto-backporting to 1.15 and 1.14 probably won't work as intended here... They 1.16 part of the diff will be misplaced on the 1.15 and 1.14 versions of the docs site.


This bug is fixed in Consul versions 1.15.2 and newer.

#### Vault Enterprise as CA ((#vault-enterprise-as-ca-1-15))
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice catch on the anchor alias ;)

@kisunji kisunji removed backport/1.14 backport/1.15 This release series is no longer active on CE. Use backport/ent/1.15. labels Oct 4, 2023
@kisunji kisunji merged commit cf9e1b6 into main Oct 4, 2023
@kisunji kisunji deleted the kisunji/vault-ca-upgrade branch October 4, 2023 20:10
jmurret pushed a commit that referenced this pull request Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport/1.16 This release series is no longer active on CE. Use backport/ent/1.16. pr/no-changelog PR does not need a corresponding .changelog entry type/docs Documentation needs to be created/updated/clarified

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants