github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-29 22:46:12 +00:00
Code Issues Projects Releases Wiki Activity
Production-Grade Container Scheduling and Management
95,055 Commits 42 Branches 7,905 Tags 1.3 GiB
Go 97%
Shell 2.6%
PowerShell 0.2%
f95ec84322
Go to file
W. Trevor King f95ec84322 Event: Document TTL and best-effort-ness 
Generally try to waive away folks who see a particular event stream
and feel tempted to extrapolate and build tooling that expects the
same underlying resource transition chain to continue to produce a
similar event stream as the underlying components evolve and are
updated.  New controllers should not be constrained to be
backwards-compatible with previous versions with regard to Event
emission.  This is distinct from the Event type itself, which has the
usual Kubernetes-API compatibility commitments for versioned types.

The EventTTL default has been 1h since 7e258b85bd (Reduce TTL for
events in etcd from 48hrs to 1hr, 2015-03-11, #5315), and remains so
today:

  $ git --no-pager log -1 --format='%h %s' origin/master
  8e5c02255c Merge pull request #90942 from ii/ii-create-pod%2Bpodstatus-resource-lifecycle-test
  $ git --no-pager grep EventTTL: 8e5c02255c cmd/kube-apiserver/app/options/options.go
  8e5c02255cc:cmd/kube-apiserver/app/options/options.go:		EventTTL:               1 * time.Hour,

In this space [1,2]:

  To avoid filling up master's disk, a retention policy is enforced:
  events are removed one hour after the last occurrence.  To provide
  longer history and aggregation capabilities, a third party solution
  should be installed to capture events.
  ...
  Note: It is not guaranteed that all events happening in a cluster
  will be exported to Stackdriver.  One possible scenario when events
  will not be exported is when event exporter is not running
  (e.g. during restart or upgrade).  In most cases it's fine to use
  events for purposes like setting up metrics and alerts, but you
  should be aware of the potential inaccuracy.
  ...
  To prevent disturbing your workloads, event exporter does not have
  resources set and is in the best effort QOS class, which means that
  it will be the first to be killed in the case of resource
  starvation.

Although that's talking more about export from etcd -> external
storage, and not about cluster components submitting events to etcd.

[1]: https://kubernetes.io/docs/tasks/debug-application-cluster/events-stackdriver/
[2]: https://github.com/kubernetes/website/pull/4155/files#diff-d8eb69c5436aa38b396d4f3ed75e4792R10
2020-10-27 15:36:37 -04:00
.github Update triage/support label references to kind/support 2020-10-01 20:09:37 -04:00
api dual stack services (#91824) 2020-10-26 13:15:59 -07:00
build Merge pull request #77398 from claudiubelu/test-images/windows-support-part-2 2020-10-26 06:19:02 -07:00
CHANGELOG CHANGELOG: Update directory for v1.20.0-alpha.3 release 2020-10-20 09:21:27 +00:00
cluster Merge pull request #95771 from vinayakankugoyal/fluentbit 2020-10-27 10:36:48 -07:00
cmd Merge pull request #95725 from p0lyn0mial/delegated-authz-sar-timeout 2020-10-27 03:37:59 -07:00
docs
hack Fix static checks for pkg/controller/podautoscaler 2020-10-23 18:53:07 +00:00
LICENSES Bump github.com/Azure/go-autorest/autorest/adal to 0.9.5 2020-10-19 09:59:45 +02:00
logo
pkg Event: Document TTL and best-effort-ness 2020-10-27 15:36:37 -04:00
plugin Move client_builder to k8s.io/controller-manager 2020-10-19 14:48:22 -07:00
staging Event: Document TTL and best-effort-ness 2020-10-27 15:36:37 -04:00
test Merge pull request #95867 from jsafrane/e2e-podexec-stderr 2020-10-26 17:55:59 -07:00
third_party
translations
vendor Merge pull request #95428 from roycaihw/cleanup/generalize-lease-controller 2020-10-23 13:43:02 -07:00
.bazelrc
.bazelversion
.generated_files
.gitattributes
.gitignore
.kazelcfg.json
BUILD.bazel
CHANGELOG.md
code-of-conduct.md
CONTRIBUTING.md
go.mod Fix dependency linting 2020-10-19 11:33:30 +02:00
go.sum Fix dependency linting 2020-10-19 11:33:30 +02:00
LICENSE
Makefile
Makefile.generated_files
OWNERS
OWNERS_ALIASES Merge pull request #94953 from mattjmcnaughton/mattjmcnaughton/remove-mattjmcnaughton-as-sig-node-reviewer 2020-10-27 10:36:01 -07:00
README.md
SECURITY_CONTACTS
SUPPORT.md
WORKSPACE

README.md

Kubernetes

GoDoc Widget CII Best Practices

Kubernetes is an open source system for managing containerized applications across multiple hosts. It provides basic mechanisms for deployment, maintenance, and scaling of applications.

Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practices from the community.

Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF). If your company wants to help shape the evolution of technologies that are container-packaged, dynamically scheduled, and microservices-oriented, consider joining the CNCF. For details about who's involved and how Kubernetes plays a role, read the CNCF announcement.

To start using Kubernetes

See our documentation on kubernetes.io.

Try our interactive tutorial.

Take a free course on Scalable Microservices with Kubernetes.

To use Kubernetes code as a library in other applications, see the list of published components. Use of the k8s.io/kubernetes module or k8s.io/kubernetes/... packages as libraries is not supported.

To start developing Kubernetes

The community repository hosts all information about building Kubernetes from source, how to contribute code and documentation, who to contact about what, etc.

If you want to build Kubernetes right away there are two options:

You have a working Go environment.
mkdir -p $GOPATH/src/k8s.io
cd $GOPATH/src/k8s.io
git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make
You have a working Docker environment.
git clone https://github.com/kubernetes/kubernetes
cd kubernetes
make quick-release

For the full story, head over to the developer's documentation.

Support

If you need support, start with the troubleshooting guide, and work your way through the process that we've outlined.

That said, if you have questions, reach out to us one way or another.