Kubernetes

remove kubernetes service-catalog finalizer with cli

由 牧云@^-^@ 提交于 2021-02-10 06:55:15
问题 I'm trying to provision/deprovision service instance/binding from my cloud provider (IBM cloud private), Currently, there is a bug that if the service is not deprovisioned in ICP, that leaves me the orphan service instance on my ICP environment which I can't delete even with force option. They provide a workaround solution of: kubectl edit ServiceInstance <service-instance-name> kubectl edit ServiceBinding <service-binding-name> then delete the line: ... finalizers: - kubernetes-incubator

openssl giving Kubernetes Ingress Controller Fake Certificate

由 故事扮演 提交于 2021-02-10 06:54:18
问题 I have configured ssl certificate, if I visit https://<domain>.com , I see that my certificate is configured successfully but when I try to check certificate by following command openssl s_client -connect <domain>.com:443 | openssl x509 -noout -subject -issuer i am getting Kubernetes Ingress Controller Fake Certificate My ingres config is : annotations: nginx.ingress.kubernetes.io/ssl-redirect: 'true' nginx.ingress.kubernetes.io/from-to-www-redirect: 'true' name: nginx-echo spec: tls: - hosts

How to mount /dev/kvm in a non-privileged pod?

由 纵饮孤独 提交于 2021-02-10 06:50:57
问题 My pod needs to access /dev/kvm but it cannot run as privileged for security reasons. How do I do this in Kubernetes? 回答1: There is a device-plugin called KVM Device Plugin that serves exactly for this purpose. This software is a kubernetes device plugin that exposes /dev/kvm from the system. 来源： https://stackoverflow.com/questions/59231393/how-to-mount-dev-kvm-in-a-non-privileged-pod

Automating wildcard subdomain support for Kubernetes using Helm operator

由 ℡╲_俬逩灬. 提交于 2021-02-10 06:50:36
问题 Here is my use case: We have a customer, where each of their services has to be available on dedicated subdomain. Naming convention should be service-name.customerdomain.com , where service-name is the deployed service and customerdomain.com is the customer domain. When a new service is created, it should be available automatically , i.e. once service-name service is deployed into the cluster, it has to be available on service-name.customerdomain.com . I know, this can be achieved manually by

Could two cluster IP services be connected in Kubernetes?

由 生来就可爱ヽ(ⅴ＜●) 提交于 2021-02-10 05:45:27
问题 The situation is that I want to connect two cluster IP services that are inside a tenant which already has Traefik as NodePort so that any of these two services can be a LoadBalancer because the NodePort is used by Traefik. The two services I am trying to connect work as follows. The first one, which I called "Master", will receive a post from the client with a text and will call the other service, called "slave", which will add some text ("Hola Patri") to the text sent by the client. The two

How to execute command from one pod inside another pod using kubectl exec which are inside a same k8s cluster

由 痴心易碎 提交于 2021-02-10 04:22:30
问题 I have two pods in a cluster. Lets call them A and B. I've installed kubectl inside pod A and I am trying to run a command inside pod B from pod A using kubectl exec -it podB -- bash . I am getting the following error Error from server (Forbidden): pods "B" is forbidden: User "system:serviceaccount:default:default" cannot create pods/exec in the namespace "default" I've created the following Role and RoleBinding to get access. Role yaml kind: Role apiVersion: rbac.authorization.k8s.io/v1

How to execute command from one pod inside another pod using kubectl exec which are inside a same k8s cluster

由 ▼魔方 西西 提交于 2021-02-10 04:22:24
问题 I have two pods in a cluster. Lets call them A and B. I've installed kubectl inside pod A and I am trying to run a command inside pod B from pod A using kubectl exec -it podB -- bash . I am getting the following error Error from server (Forbidden): pods "B" is forbidden: User "system:serviceaccount:default:default" cannot create pods/exec in the namespace "default" I've created the following Role and RoleBinding to get access. Role yaml kind: Role apiVersion: rbac.authorization.k8s.io/v1

如何管理越来越多的Operator？OLM给你答案

由 本小妞迷上赌 提交于 2021-02-09 20:27:45
作者 | 匡大虎、阚俊宝 导读： OLM(Operator Lifecycle Manager) 作为 Operator Framework 的一部分，可以帮助用户进行 Operator 的自动安装，升级及其生命周期的管理。同时 OLM 自身也是以 Operator 的形式进行安装部署，可以说它的工作方式是以 Operators 来管理 Operators，而它面向 Operator 提供了声明式 (declarative) 的自动化管理能力也完全符合 Kubernetes 交互的设计理念。本文我们将来了解一下 OLM 的基本架构和安装使用。 OLM 组件模型定义 OLM 的出现是为了帮助没有如大数据，云监控等领域知识的用户能够自助式地部署并管理像 etcd、大数据分析或监控服务等复杂的分布式应用。因此从它的设计目标来说，OLM 官方希望实现面向云原生应用提供以下几个方向上的通用管理能力，包括： 生命周期管理：管理 operator 自身以及监控资源模型的升级和生命周期； 服务发现：发现在集群中存在哪些 operator，这些 operators 管理了哪些资源模型以及又有哪些 operators 是可以被安装在集群中的； 打包能力：提供一种标准模式用于 operator 以及依赖组件的分发，安装和升级； 交互能力：在完成了上述能力的标准化后，还需要提供一种规范化的方式（如 CLI

【Kubernetes社区之路】kubernetes机器人指令介绍

由 泄露秘密 提交于 2021-02-09 14:12:19
Prow 是kubernetes社区使用的CI/CD系统，基于kubernetes实现，它提供了一系列 /foo 格式的命令供用户使用。使用这些指令，可以让机器人完成相应的工作，例如，当你提交PR后，可以使用 /assign @<somebody> 命令来指定一个owner来审核你的PR。 当开发者提交PR（Pull Request）到kubernetes社区时，机器人会自动回复你，并在回复中指示当前PR的状态或者指示你下一步该如何做，别人也会在你的PR中回复一些机器人命令，所以，做为开发者有必要清楚的了解常用的一些命令。 下面介绍一些比较常见的命令，更多的命令可以查阅官方介绍（ https://prow.k8s.io/command-help）。 TODO: 或许可以按照标签操作类、流程控制类、其他来分类 重跑失败的用例：/retest 顾名思义，这个命令用于重新执行失败的测试（有时自动化测试会因环境因素而失败），由于只有PR才会触发自动化测试，所以这个命令仅用于PR中。 用法举例： /retest ： 重启失败的测试 使用条件： 只能用于可信的PR，即包含 ok-to-test 标签的PR； 任何人都可以使用； 命令效果： 重新启动失败的测试； 图示如下： 手动触发测试用途：/test /test 用于手动执行某个或全部测试用例，有些用例并没包括在自动化测试用例范围内

Does Istio support hazelcast-kubernetes?

由 江枫思渺然 提交于 2021-02-09 11:49:49
问题 I am using istio 1.0.2 version with istio-demo-auth .yaml, and I used hazelcast-kubernetes in the k8s cluster environment. I was using hazelcast-kubernetes in the k8s cluster before, when scale two hazelcast-kubernetes StatefulSet, they can join together, and working with my services. Not using istio that time. Recently our services injected with istio. I try to inject the hazelcast-kubernetes with istio, it was running, but those two hazelcast-kubernetes cannot join together. Do you know how
订阅 Kubernetes