k8s
Here are 2,843 public repositories matching this topic...
Overview
First off, thanks to all of you who work on K3s. It's such an awesome service. I have a use-case which requires running K3s on Docker. I'm following Using Docker as the Container Runtime. I realized after running the K3s install (see version / arguments below) that I also had to install Doc
Is your feature request related to a problem? Please describe.
Because manipulating kubernetes often requires changing configmap and/or secrets, it is fair to presume that one would use the create/edit feature to enter sensitive informatio
Description
Expected Behavior
it should just work ;^) But if not it needs to feed the errored state back somehow.
in this case it probably needs to say that the disk is already mounted.
## Current Behavior
<!-- Tell us what happens instead -->
Repro'ed:
bmath@timesink:~/maya/gke/test86$ ca
Bug report
General Information
- Cilium version: 1.7.2
- Kernel version: 5.6.6
- Orchestration system version: Kubernetes 1.18.2
I'm using terraform to spool and deploy kubeadm on AWS.
How to reproduce the issue
The issues is that if the Cloud Controller Manager is not brought up before Cilium the node is brought, and the operator starts running ENIs will be attached t
# 创建https ingress
$ kubectl apply -f /etc/ansible/manifests/ingress/traefik/tls/hello-tls.ing.yaml
# 注意根据hello示例,需要在default命名空间创建对应的secret: traefik-cert
$ kubectl create secret tls traefik-cert --key=tls.key --cert=tls.crt
- 不执行 hello-tls.ing.yaml ,nginx的https
-
Updated
Jul 16, 2020 - JavaScript
There are a few samples at https://kubesphere.io/docs/quick-start/admin-quick-start/ helping users how to use KubeSphere. It would be better to create tutorial videos in English for these samples so that we can distribute them in some channels such as Youtube making more people get familiar with KubeSphere.
So call for English native speaker from the community to help us.
As a microk8s user on Windows/Mac, I want to be able to use a standard kubectl for all my K8s instances that run on my machine.
A solution to that would be to have the installers detect any pre-existing kubeconfig files in the system and automatically append the microk8s context to them. Essentially, the installers need to automate this procedure: https://kubernetes.io/docs/tasks/access-applic
When deploying hasura example - mono repo with k8s, git push is failing with
$ git push minikube master
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
When creating myremote, I have used ~/.ssh/id_ras.pub and it wasn't changed. Not sure wh
Hi :) I am Na Eun Kwon a university student in Kwangwoon University. I want to translate READ ME documentation for your project contribution and other Koreans who want to learn about kubernetes.
So may I translate these infos into Korean?
If I could, plz tell me how I can share the translated results.
Thank you
可视化方式展示防火墙状态,方便异常排错
能够以可视化方式显示 KO 部署机本身,及集群中各个主机的防火墙运行情况。
Feature motivation
Azure storage client is backward incompatible, there's an issue #757 for upgrading the azure connection to the latest client. The new version has an async interface that can be leveraged for the streams module, at least for downloads.
N.B. This is likely a 3~4h work and not a pressing need, so just putting this in the backlog.
Feature implementation
There's a
Docker Bulid 安装依赖失败问题The command '/bin/sh -c pip3 install --upgrade pip' returned a non-zero code: 1
错误信息:
Step 10/16 : RUN pip3 install --upgrade pip
---> Running in 83716c526776
Collecting pip
Downloading https://files.pythonhosted.org/packages/c2/d7/90f34cb0d83a6c5631cf71dfe64cc1054598c843a92b400e55675cc2ac37/pip-18.1-py2.py3-none-any.whl (1.3MB)
Installing collected packages: pip
Found existing installation: pip 10.0.1
Uninstalling pip-10.0.1:
Successfully uninstalled
-
Updated
Jul 16, 2020
This feature enables the ipsec backend for Flannel in the k3sup install command
Expected Behaviour
An additional flag to k3sup install should enable ipsec for Flannel as
This came up while discussing to release popeye as a kubectl plugin. See kubernetes-sigs/krew-index#521 (comment) for details.
This is merely a reminder that it would be nice to fix it at some point.
Kata shimv2 does not have any tracing yet. Will be useful to add this.
-
Updated
Jul 7, 2020 - Go
-
Updated
Jul 16, 2020
At Cognite, we've had to patch faas-netes as a workaround for openfaas/faas-netes#604 and openfaas/faas-netes#358. We use helm to produce a manifest that we then modify before it is deployed in our k8s clusters, so I need to modify which image I use.
The list over options at the end of https://github.com/openfaas/faas-netes/tree/master/chart/
-
Updated
Jul 16, 2020 - Go
Since this has transitioned to using an in repo helm chart, the helm chart documentation should be checked, and documented. The current helm chart in this repo, seems to be built from several layers of templating which makes it harder to understand, and the correctness of this documentation all the more essential.
- The last Helm Stable repo version had the appropriate section documenting the
deis logs -a <app_name> --lines -1 not spitting out all logs since app launch. As a workaround you have to supply an arbitrarily large number i.e - deis logs -a <app_name> --lines 10000.
Cloudprober supports building additional metrics (other than the default ones) from external probe output. We could possible do the same for HTTP probe.
-
Updated
Jul 26, 2019 - Shell
Summary
Kong Ingress Controller touches all ingresses, regardless of "kubernetes.io/ingress.class".
Kong Ingress controller version
0.7.0 (with 0.7.1 is the same)
Kong or Kong Enterprise version
1.4 (I tried also 1.5.0)
Kubernetes version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89",
-
Updated
Jun 29, 2020 - Shell
Improve this page
Add a description, image, and links to the k8s topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the k8s topic, visit your repo's landing page and select "manage topics."

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