Kubernetes

Kubernetes (commonly referred to as "K8s") is an open source system for automating deployment, scaling and management of containerized applications originally designed by Google and donated to the Cloud Native Computing Foundation. It aims to provide a "platform for automating deployment, scaling, and operations of application containers across clusters of hosts". It supports a range of container tools, including Docker.
Here are 16,385 public repositories matching this topic...
Feature idea summary
Cgroups plugin supports only proportional and max Block IO policies. We should support BFQ scheduler as well. Disk stats for the scheduler are in blkio.bfq.io_service_bytes
and blkio.bfq.io_serviced
files.
-
Updated
Feb 12, 2021 - Go
-
Updated
Feb 13, 2021 - Go
Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13
Internet says it should return 204:
- https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
- https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests
Internet changed its mind since 2018 https://
-
Updated
Feb 14, 2021 - Go
-
Updated
Feb 14, 2021 - Shell
here we confuse the user with two things
and
we should had sticked with first advice
drewpca(pts/0):~% minikube start -p foo --memory 6GB
😄 [foo] m
Move all Dockerfile samples to non-root user
Expected Behaviour
As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.
Current Behaviour
Helm documentation states the following:
-1) (k8s) metadata.name is restricted to a maximum length of 63 characters because of limitations to the DNS system
-2) For that reasons, release names are (DNS labels that are) limited to 53 characters
Statement 1) is not correct.
k8s does not impose a max length of 63 characters on resource names.
The actual max length for a resource name is 253 c
-
Updated
Jan 19, 2021 - Go
-
Updated
Feb 14, 2021 - JavaScript
Beta release: Grayscale release can not select client IP needs to be filled in manually, hope to add support to select IP directly from the connected client
Beta发布: 灰度发布不能选择客户端ip 需要手动填写,希望增加支持从已连接的客户端直接选择ip
-
Updated
Feb 14, 2021 - Go
-
Updated
Feb 6, 2021 - JavaScript
1. Describe IN DETAIL the feature/behavior/change you would like to see.
Using AWS GovCloud is a bit different from the regular AWS.
https://github.com/kubernetes/kops/blob/master/docs/getting_started/aws.md
2. Feel free to provide a design supporting your feature request.
Kops v1.18.2 improves the support for AWS GovCloud and should work without any additional tweaks, except for
-
Updated
Feb 14, 2021 - Go
Problem Statement
There are users who would like to secure the http port exported by the vitess servers with TLS. However, some of the health check and monitoring URLs (like /debug/vars
) still need to be accessed without TLS. For example, Kubernetes prefers the health check URLs to not require TLS.
We require the ability to specify a separate (optional) TLS http port, and the ability to s
https://github.com/verdaccio/monorepo/blob/9.x/core/types/index.d.ts defines
type AuthAccessCallback = (error: string | null, access: boolean) => void;
interface IPluginAuth<T> extends IPlugin<T> {
authenticate(user: string, password: string, cb: AuthCallback): void;
adduser?(user: string, password: string, cb: AuthCallback): void;
changePassword?(user: string, password: stri
-
Updated
Feb 11, 2021 - Shell
This is a request for implementing the --post-render flag in helm to be able to execute things like:
helm install mychart stable/wordpress --post-renderer ./path/to/executable
In particular the aim is to use kustomize as a followup of the helm.
Expected behavior
a key to be added to the helm's deploy
Actual behavior
No such option
Information
- Skaffold version: NA
Currently validating checksums requires lots of knowledge on the part of the caller. We should expose optional checksum validation in our existing validation functions e.g. IPv4.IsValid
.
header.UDP and header.TCP don't currently have these functions; we should add them.
-
Updated
Feb 6, 2021 - Go
I want to use the "ecr-login" credHelper for both from
and to
, but I need to use different environment variables (AWS_PROFILE
in my case), because the IAM is different in each case. If it is possible somehow, I would like to know, and if not, I would like to request this feature (just like e.g. environment
can be set for dockerClient
).
As a workaround, I will now try to run the credHe
FEATURE REQUEST:
Hi,
I see that there is nothing in the kargo repo related to docker login
stuff and more precisely nothing about the ability to make kubernetes pull images from private registries such as ECR.
I have a solution for this that currently works for ECR and CoreOS and that could be extended to different registries solutions (azure one, custom private registry on premi
/kind feature
This is a sub-issue from #5494.
We need to remove any f"strings"
from the backend of the Jupyter web app in order to be able to use lower versions from Python 3.6 to run it.
/good-first-issue
NGINX Ingress controller version: 0.44.0
NGINX Ingress controller Helm Chart version: 3.23.0
Kubernetes version: v1.20.2
Environment:
- Cloud provider or hardware configuration: AWS
- OS: CentOS Linux release 7.7.1908 (Core)
- Kernel: 3.10.0-1160.11.1.el7.x86_64
What happened:
when trying to deploy this chart using the following:
helm repo
Created by @jbeda, @brendandburns, and @craigmcl
Released July 21, 2015
Latest release about 1 month ago
- Repository
- kubernetes/kubernetes
- Website
- kubernetes.io
- Wikipedia
- Wikipedia
Inspired by #98726
There are a lot of tests (pkg/apis/networking/validation/validation_test.go in that PR) that have tables of structures like Service or NetworkPolicy, where the struct has to be complete enough (e.g. to pass validation) but each test-case only modifies one tiny section of the otherwise boilerplate struct.
The result is a LOT of noise which makes the actual differences hard