mirror of https://github.com/k3s-io/kubernetes.git synced 2026-01-15 22:38:07 +00:00

Files

Saverio Proto bdc54eb18a Use compute v1 api to specify network tier

Drop the use of the alpha api for operations that are supported by compute v1

The switch/case logic was wrong because the user
can set the default tier for a project:
https://cloud.google.com/network-tiers/docs/using-network-service-tiers#setting_the_tier_for_all_resources_in_a_project

The assumption that the default tier is always PREMIUM is wrong

This patch uses the explicit network tier when possible,
or it falls back to the project default.

Signed-off-by: Saverio Proto <saverioproto@google.com>

2020-02-25 08:16:58 +01:00

publishing

Add release-1.18 publishing rules

2020-02-22 19:42:34 -05:00

src

Use compute v1 api to specify network tier

2020-02-25 08:16:58 +01:00

BUILD

…

OWNERS

…

README.md

Drop k8s.io/node-api packages

2020-02-07 10:07:14 -05:00

repos_generated.bzl

proxier: use IPSet from k8s.io/utils/net to store local addresses

2020-02-11 16:44:34 -05:00

README.md

External Repository Staging Area

This directory is the staging area for packages that have been split to their own repository. The content here will be periodically published to respective top-level k8s.io repositories.

Repositories currently staged here:

The code in the staging/ directory is authoritative, i.e. the only copy of the code. You can directly modify such code.

Using staged repositories from Kubernetes code

Kubernetes code uses the repositories in this directory via symlinks in the vendor/k8s.io directory into this staging area. For example, when Kubernetes code imports a package from the k8s.io/client-go repository, that import is resolved to staging/src/k8s.io/client-go relative to the project root:

// pkg/example/some_code.go
package example

import (
  "k8s.io/client-go/dynamic" // resolves to staging/src/k8s.io/client-go/dynamic
)

Once the change-over to external repositories is complete, these repositories will actually be vendored from k8s.io/<package-name>.

Creating a new repository in staging

Adding the staging repository in `kubernetes/kubernetes`:

Send an email to the SIG Architecture mailing list and the mailing list of the SIG which would own the repo requesting approval for creating the staging repository.
Once approval has been granted, create the new staging repository.
Add a symlink to the staging repo in vendor/k8s.io.
Update import-restrictions.yaml to add the list of other staging repos that this new repo can import.
Add all mandatory template files to the staging repo as mentioned in https://github.com/kubernetes/kubernetes-template-project.
Make sure that the .github/PULL_REQUEST_TEMPLATE.md and CONTRIBUTING.md files mention that PRs are not directly accepted to the repo.

Creating the published repository

Create an issue in the kubernetes/org repo to request creation of the respective published repository in the Kubernetes org. The published repository must have an initial empty commit. It also needs specific access rules and branch settings. See #kubernetes/org#58 for an example.
Setup branch protection and enable access to the stage-bots team by adding the repo in prow/config.yaml. See #kubernetes/test-infra#9292 for an example.
Once the repository has been created in the Kubernetes org, update the publishing-bot to publish the staging repository by updating:
- rules.yaml: Make sure that the list of dependencies reflects the staging repos in the Godeps.json file.
- fetch-all-latest-and-push.sh: Add the staging repo in the list of repos to be published.
Add the staging and published repositories as a subproject for the SIG that owns the repos in sigs.yaml.
Add the repo to the list of staging repos in this README.md file.

README.md

External Repository Staging Area

Using staged repositories from Kubernetes code

Creating a new repository in staging

Adding the staging repository in kubernetes/kubernetes:

Creating the published repository

Adding the staging repository in `kubernetes/kubernetes`: