mirror of https://github.com/k3s-io/kubernetes.git synced 2026-01-13 19:36:22 +00:00

Files

Patrick Ohly 1aceac797d logs: make LoggingConfiguration an unversioned API

Making the LoggingConfiguration part of the versioned component-base/config API
had the theoretic advantage that components could have offered different
configuration APIs with experimental features limited to alpha versions (for
example, sanitization offered only in a v1alpha1.KubeletConfiguration). Some
components could have decided to only use stable logging options.

In practice, this wasn't done. Furthermore, we don't want different components
to make different choices regarding which logging features they offer to
users. It should always be the same everywhere, for the sake of consistency.

This can be achieved with a saner Go API by dropping the distinction between
internal and external LoggingConfiguration types. Different stability levels of
indidividual fields have to be covered by documentation (done) and potentially
feature gates (not currently done).

Advantages:

- everything related to logging is under component-base/logs;
  previously this was scattered across different packages and
  different files under "logs" (why some code was in logs/config.go
  vs. logs/options.go vs. logs/logs.go always confused me again
  and again when coming back to the code):

  - long-term config and command line API are clearly separated
    into the "api" package underneath that

  - logs/logs.go itself only deals with legacy global flags and
    logging configuration

- removal of separate Go APIs like logs.BindLoggingFlags and
  logs.Options

- LogRegistry becomes an implementation detail, with less code
  and less exported functionality (only registration needs to
  be exported, querying is internal)

2022-06-17 20:22:13 +02:00

publishing

Update publishing-bot rules for Go 1.17.11

2022-06-07 15:56:48 +02:00

src/k8s.io

logs: make LoggingConfiguration an unversioned API

2022-06-17 20:22:13 +02:00

OWNERS

…

README.md

staging-readme: Document the need to add doc.go in a staging repo

2022-06-16 13:48:13 +01: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.
Ensure that docs.go file is added. Refer to #kubernetes/kubernetes#91354 for reference.
NOTE: Do not edit go.mod or go.sum in the new repo (staging/src/k8s.io//) manually. Run the following instead:

  ./hack/update-vendor.sh

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`: