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

Document Antrea versioning #1352

Merged
merged 5 commits into from
Oct 22, 2020

Conversation

antoninbas
Copy link
Contributor

Fixes #1273

@antrea-bot
Copy link
Collaborator

Thanks for your PR.
Unit tests and code linters are run automatically every time the PR is updated.
E2e, conformance and network policy tests can only be triggered by a member of the vmware-tanzu organization. Regular contributors to the project should join the org.

The following commands are available:

  • /test-e2e: to trigger e2e tests.
  • /skip-e2e: to skip e2e tests.
  • /test-conformance: to trigger conformance tests.
  • /skip-conformance: to skip conformance tests.
  • /test-whole-conformance: to trigger all conformance tests on linux.
  • /skip-whole-conformance: to skip all conformance tests on linux.
  • /test-networkpolicy: to trigger networkpolicy tests.
  • /skip-networkpolicy: to skip networkpolicy tests.
  • /test-windows-conformance: to trigger windows conformance tests.
  • /skip-windows-conformance: to skip windows conformance tests.
  • /test-windows-networkpolicy: to trigger windows networkpolicy tests.
  • /skip-windows-networkpolicy: to skip windows networkpolicy tests.
  • /test-hw-offload: to trigger ovs hardware offload test.
  • /skip-hw-offload: to skip ovs hardware offload test.
  • /test-all: to trigger all tests (except whole conformance).
  • /skip-all: to skip all tests (except whole conformance).

@codecov-io
Copy link

codecov-io commented Oct 8, 2020

Codecov Report

Merging #1352 into master will decrease coverage by 10.02%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##           master    #1352       +/-   ##
===========================================
- Coverage   64.32%   54.30%   -10.03%     
===========================================
  Files         159      120       -39     
  Lines       12674    11266     -1408     
===========================================
- Hits         8153     6118     -2035     
- Misses       3668     4554      +886     
+ Partials      853      594      -259     
Flag Coverage Δ
#integration-tests 44.82% <ø> (-0.04%) ⬇️
#kind-e2e-tests ?
#unit-tests 42.05% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
pkg/agent/agent_linux.go 0.00% <0.00%> (-100.00%) ⬇️
pkg/agent/proxy/types/groupcounter.go 0.00% <0.00%> (-95.00%) ⬇️
pkg/controller/networkpolicy/tier.go 0.00% <0.00%> (-90.00%) ⬇️
pkg/apis/controlplane/register.go 0.00% <0.00%> (-85.72%) ⬇️
pkg/agent/proxy/types/types.go 0.00% <0.00%> (-84.62%) ⬇️
pkg/apis/stats/register.go 0.00% <0.00%> (-81.82%) ⬇️
pkg/agent/client.go 0.00% <0.00%> (-77.42%) ⬇️
pkg/agent/util/ethtool/ethtool_linux.go 0.00% <0.00%> (-70.00%) ⬇️
pkg/apis/controlplane/v1beta1/helper.go 0.00% <0.00%> (-69.24%) ⬇️
pkg/k8s/name.go 33.33% <0.00%> (-66.67%) ⬇️
... and 98 more


## Table of Contents

<!-- toc -->
Copy link
Contributor

Choose a reason for hiding this comment

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

yay!

docs/versioning.md Show resolved Hide resolved
releases](https://kubernetes.io/docs/setup/release/version-skew-policy/#supported-versions)
at the time of release (3 up to K8s 1.19, 4 after that). For example, at the
time that Antrea 0.10 was released, the latest K8s version was 1.19; as a result
we guarantee that 0.10 supports at least 1.19, 1.18 and 1.17 (in practice is
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
we guarantee that 0.10 supports at least 1.19, 1.18 and 1.17 (in practice is
we guarantee that 0.10 supports at least 1.19, 1.18 and 1.17 (in practice it


Eventually, even a stable metric can be deleted. In this case, the metric must
be marked as deprecated first and the metric must stay deprecated for at least
one minor release. The [CHANGELOG] must announced both metric deprecations and
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
one minor release. The [CHANGELOG] must announced both metric deprecations and
one minor release. The [CHANGELOG] must announce both metric deprecations and

guarantee](#antrea-upgrade-and-supported-version-skew). The `controlplane` API
(which is exposed using the aggregation layer) is often referred to as an
"internal" API as it is used by the Antrea components to communicate with each
other, and is usually noit consummed by end users, e.g. cluster admins. However,
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
other, and is usually noit consummed by end users, e.g. cluster admins. However,
other, and is usually not consumed by end users, e.g. cluster admins. However,

abhiraut
abhiraut previously approved these changes Oct 10, 2020
Copy link
Member

@tnqn tnqn left a comment

Choose a reason for hiding this comment

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

Thanks for the summary, looks very clear. Some typos.


Unlike minor releases, patch releases should not contain miscellaneous feature
additions or improvements. No incompatibilities should ever be introduced
between patch version of the same minor version. API groups / versions must not
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
between patch version of the same minor version. API groups / versions must not
between patch versions of the same minor version. API groups / versions must not

?

updated (from `Alpha` to `Beta` or from `Beta` to `GA`). Refer to the the
[CHANGELOG] for information about feature stability level for each release. For
features controlled by a feature gate, this information is also present in a
more structured way in [features-gates.md](features-gate.md).
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
more structured way in [features-gates.md](features-gate.md).
more structured way in [features-gates.md](feature-gates.md).

patch support. This may seem short, but was done on purpose to encourage users
to upgrade Antrea often and avoid potential incompatibility issues. In the
future, we may reduce our release cadence for minor releases and simultaneously
increase the support windows for each release.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
increase the support windows for each release.
increase the support window for each release.

?

When directly applying a newer Antrea YAML manifest, as provided for each
[release](https://github.com/vmware-tanzu/antrea/releases), there is no
guarantee that the Antrea Controller will be upgraded first. In practice, the
Controller would be upgraded simultaneously with the first Agents to be upgraded
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
Controller would be upgraded simultaneously with the first Agents to be upgraded
Controller would be upgraded simultaneously with the first Agent to be upgraded

also supports K8s 1.16).

In addition, we strive to support the K8s versions used by default in
cloud-managed K8s services ([EKS], [AKS] and [GKE (regular channel)]).
Copy link
Member

Choose a reason for hiding this comment

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

[GKE (regular channel)] doesn't appear as link


K8s has a [moratorium](https://github.com/kubernetes/kubernetes/issues/52185) on
the removal of API object versions that have been persisted to storage. At the
moment, node of Antrea APIServices (which use the aggregation layer) persist
Copy link
Member

Choose a reason for hiding this comment

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

Do you mean "none of Antrea APIServices"?

tnqn
tnqn previously approved these changes Oct 15, 2020
Copy link
Member

@tnqn tnqn left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Member

@srikartati srikartati left a comment

Choose a reason for hiding this comment

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

Just one comment on Prometheus deprecation policy link.

### Prometheus metrics deprecation policy

Antrea follows a similar policy as
[Kubernetes](https://cloud.google.com/kubernetes-engine/docs/release-notes) for
Copy link
Member

Choose a reason for hiding this comment

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

I could not find any Prometheus deprecation policy for K8s in the link https://cloud.google.com/kubernetes-engine/docs/release-notes. Wondering if that is the intended link.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks. Looks like I got my links confused, will fix

@antoninbas
Copy link
Contributor Author

/skip-all

@antoninbas antoninbas merged commit 51d6487 into antrea-io:master Oct 22, 2020
@antoninbas antoninbas deleted the document-antrea-versioning branch October 22, 2020 22:10
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.

Document Antrea version lifecycle
7 participants