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

Release 0.20 #1198

Merged
merged 13 commits into from
Dec 11, 2020
Merged

Release 0.20 #1198

merged 13 commits into from
Dec 11, 2020

Conversation

wilsonehusin
Copy link
Contributor

@wilsonehusin wilsonehusin commented Dec 10, 2020

What this PR does / why we need it:
Version bumps for v0.20.0 release

Which issue(s) this PR fixes
None

Special notes for your reviewer:

Release note:

NONE

README.md Outdated Show resolved Hide resolved
scripts/update_docs.sh Show resolved Hide resolved
pkg/image/manifest.go Show resolved Hide resolved
Copy link
Contributor

@vladimirvivien vladimirvivien left a comment

Choose a reason for hiding this comment

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

I think that's enough for now.

README.md Outdated Show resolved Hide resolved
README.md Outdated
@@ -15,7 +15,10 @@ for the following use cases:
* Workload debugging
* Custom data collection via extensible plugins

Sonobuoy supports 3 Kubernetes minor versions: the current release and 2 minor versions before. Sonobuoy is currently versioned to track the Kubernetes minor version to clarify the support matrix. For example, Sonobuoy v0.14.x would support Kubernetes 1.14.x, 1.13.x, and 1.12.x.
Starting v0.20, Sonobuoy supports Kubernetes v1.17 or earlier.
Sonobuoy no longer follows Kubernetes release cycle -- this means that Sonobuoy releases in the future may not follow the same cadence as Kubernetes releases.
Copy link
Contributor

Choose a reason for hiding this comment

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

Probably just say that Sonobuoy releases will be independent and not necessarily coincide with a Kubernetes release.

README.md Outdated
Sonobuoy supports 3 Kubernetes minor versions: the current release and 2 minor versions before. Sonobuoy is currently versioned to track the Kubernetes minor version to clarify the support matrix. For example, Sonobuoy v0.14.x would support Kubernetes 1.14.x, 1.13.x, and 1.12.x.
Starting v0.20, Sonobuoy supports Kubernetes v1.17 or earlier.
Sonobuoy no longer follows Kubernetes release cycle -- this means that Sonobuoy releases in the future may not follow the same cadence as Kubernetes releases.
Sonobuoy will continually ensure that new releases continue to work functionally.
Copy link
Contributor

Choose a reason for hiding this comment

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

continually

README.md Outdated
@@ -117,14 +120,14 @@ issue][issue].

### Docker Hub rate limit

We're planning to release v0.20.0 with a better user interface. Until then, this is the usable workaround.
We're planning a future release with a better user interface. Until then, this is the usable workaround.
Copy link
Contributor

Choose a reason for hiding this comment

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

Possibly add a tidbit about Docker Hub rate limiting... "This year, Docker has started rate limiting image pulls from Docker hub. This release introduces a workaround when using Sonobuoy (future release will come with a better user experience" or something similar to that (sorry for all these words).

@@ -15,7 +15,7 @@ for the following use cases:
* Workload debugging
* Custom data collection via extensible plugins

Starting v0.20, Sonobuoy supports Kubernetes v1.17 or earlier.
Starting v0.20, Sonobuoy supports Kubernetes v1.17 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.

Maybe we should do 1.14 or earlier (if it's no code change).


Starting v0.20, Sonobuoy supports Kubernetes v1.17 or later.
Sonobuoy no longer follows Kubernetes release cycle -- this means that Sonobuoy releases in the future may not follow the same cadence as Kubernetes releases.
Sonobuoy will continually ensure that new releases continue to work functionally.
Copy link
Contributor

Choose a reason for hiding this comment

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

continually

* Custom data collection via extensible plugins

Starting v0.20, Sonobuoy supports Kubernetes v1.17 or later.
Sonobuoy no longer follows Kubernetes release cycle -- this means that Sonobuoy releases in the future may not follow the same cadence as Kubernetes releases.
Copy link
Contributor

Choose a reason for hiding this comment

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

Makes it sound affirmative that Sonobuoy will not follow kubernetes release cadance.


#### Conformance

Kubernetes end-to-end conformance test pulls several images from Docker Hub as part of testing. To override this, save the following file locally (e.g. `conformance-image-config.yaml`):
Copy link
Contributor

Choose a reason for hiding this comment

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

should read ... save the following to a file

Copy link
Contributor

Choose a reason for hiding this comment

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

Actually, let's reword this sentence to say soemthing like
... To override this, you will need to create a registry manifest file by saving the following to a local file ...

site/docs/v0.20.0/README.md Show resolved Hide resolved

## Known Issues

### Docker Hub rate limit
Copy link
Contributor

Choose a reason for hiding this comment

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

Let's make this it's own section. Take it outside of Know Issue so it will stand out.

Docker Hub Rate Limits

pkg/image/manifest.go Show resolved Hide resolved
Wilson E. Husin and others added 13 commits December 11, 2020 14:39
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
Don't assume that dev machines install bash in /bin/bash

Signed-off-by: Wilson E. Husin <whusin@vmware.com>
TODO: airgap + blog
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
Signed-off-by: Wilson E. Husin <whusin@vmware.com>
@wilsonehusin wilsonehusin merged commit f6e1914 into vmware-tanzu:master Dec 11, 2020
@wilsonehusin wilsonehusin deleted the release-0.20 branch December 11, 2020 23:11
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