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

chore: release 15.0.0 #897

Merged
merged 3 commits into from
Jun 8, 2021
Merged

chore: release 15.0.0 #897

merged 3 commits into from
Jun 8, 2021

Conversation

release-please[bot]
Copy link
Contributor

@release-please release-please bot commented May 17, 2021

🤖 I have created a release *beep* *boop*

15.0.0 (2021-06-08)

⚠ BREAKING CHANGES

Features

  • Add multi-repo support for Config Sync (#872) (23da103)
  • Add support for enable_l4_ilb_subsetting flag (#896) (7531f90)
  • Add use local_ssd_ephemeral_count attribute in node_pool config on beta clusters (#902) (9335262)
  • K8s provider upgrade (#892) (9172b3e)
  • Updated ASM terraform module for 1.8 and 1.9 (#895) (e2ba8d2)

Bug Fixes

  • Add ability to impersonate service accounts in kubectl for all submodules (#903) (fc43485)
  • asm destroy (#922) (f3ddbf5)
  • Asm overlay path (#921) (5d3dc52)
  • docs: Describe ADVANCED_DATAPATH in more detail (#907) (c32c5d1)
  • Ensure the ASM module's destroy command removes all ASM components (#918) (00c2b71)
  • switch ASM API and IAM flags to use native resources (#914) (ff71123)

This PR was generated with Release Please. See documentation.

@comment-bot-dev
Copy link

comment-bot-dev commented May 17, 2021

Thanks for the PR! 🚀
✅ Lint checks have passed.

@release-please release-please bot force-pushed the release-v15.0.0 branch 2 times, most recently from 8016750 to c121904 Compare May 17, 2021 20:33
@Jberlinsky
Copy link
Contributor

Jberlinsky commented May 18, 2021

@bharathkkb I have a commit in here, so I'm not comfortable self-LGTMing :)

IHAC who is going to need this (ILB subsetting support) in the imminent future -- any ETA to get this released?

@morgante
Copy link
Contributor

@Jberlinsky Can they reference the release branch for now? In general we avoid rushing releases.

@Jberlinsky
Copy link
Contributor

Absolutely -- just looking for a broad-strokes idea of days/weeks/months to manage expectations :)

@bharathkkb
Copy link
Member

@Jberlinsky we usually aim for 2 weeks, we will need an upgrade guide due to some breaking changes.

@release-please release-please bot force-pushed the release-v15.0.0 branch 3 times, most recently from 736ee0d to 692214b Compare May 20, 2021 23:50
@morgante
Copy link
Contributor

@bharathkkb Do we need an upgrade guide here? It seems the main breaking change is for ASM and I'm not sure if we actually support upgrade there.

@bharathkkb
Copy link
Member

@morgante yeah we do not support upgrades for ASM currently, although I do want to resolve #905 to prevent another breaking change. Provider bumps should be no-op but we have historically documented these.

@morgante
Copy link
Contributor

Provider bumps should be no-op but we have historically documented these.

Yes we should make sure to include that in the release notes (you can simply edit the markdown on this PR).

@release-please release-please bot force-pushed the release-v15.0.0 branch 3 times, most recently from 7591758 to 919a50b Compare June 7, 2021 20:56
@bharathkkb bharathkkb merged commit a93cc5a into master Jun 8, 2021
@release-please
Copy link
Contributor Author

release-please bot commented Jun 8, 2021

@apeabody apeabody deleted the release-v15.0.0 branch July 19, 2022 20:47
CPL-markus pushed a commit to WALTER-GROUP/terraform-google-kubernetes-engine that referenced this pull request Jul 15, 2024
* chore: release 15.0.0

* Update CHANGELOG.md

* Update CHANGELOG.md

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Co-authored-by: Bharath KKB <bharathkrishnakb@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants