fabric8

Forbidden: updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden

由 半城伤御伤魂 提交于 2019-12-11 03:36:40
问题 I use io.fabric8.kubernetes-client, version 3.1.8 to do RollingUpdate of kubernetes resource. It is fine for Deployment. But I meet an exception for StatefulSet. But it is also fine if I use 'kubectl apply -f ***.yaml' for the StatefulSet. Code to RollingUpdate Deployment: public void createOrReplaceResourceByYaml(String namespace, KubernetesResource resource) { KubernetesClient client = k8sRestClient.newKubeClient(); Deployment deployment = (Deployment) resource; logger.info(String.format(

gofabric8> Unable to unzip /Users/apple/.fabric8/bin/oc.zip zip: not a valid zip

由 拈花ヽ惹草 提交于 2019-12-11 02:44:46
问题 I'm trying to set up environment for microservices. I'm using fabric8 to do that. I'm using mvn fabric8:cluster-start -Dfabric8.cluster.kind=openshift command. while executing i'm getting following error... [INFO] gofabric8> Downloading https://github.com/openshift/origin/releases/download/v1.3.1/openshift-origin-client-tools-v1.3.1-dad658de7465ba8a234a4fb40b5b446a45a4cee1-mac.zip... [INFO] gofabric8> **Unable to unzip /Users/apple/.fabric8/bin/oc.zip zip: not a valid zip fileUnable to

best way in Kubernetes to receive notifications of errors when instantiating resources from .json or .yaml specifications?

由 試著忘記壹切 提交于 2019-12-11 01:06:09
问题 I am using fabric8 to develop a cluster management layer on top of Kubernetes, and I am confused as to what the 'official' API is to obtain notifications of errors when things go wrong when instantiating pods/rep controllers & services etc. In the section "Pod Deployment Code" I have a stripped down version of what we do for pods. In the event that everything goes correctly, our code is fine. We rely on setting 'watches' as you can see in the method deployPodWithWatch . All I do in the given

Programmatically get the name of the pod that a container belongs to in Kubernetes?

由 孤者浪人 提交于 2019-12-08 23:53:46
问题 Is there a way to programmatically get the name of the pod that a container belongs to in Kubernetes? If so how? I'm using fabric8's java client but curl or something similar will be fine as well. Note that I don't want to find the pod using a specific label since then (I assume) I may not always find the right pod if it's scaled with a replication controller. 回答1: You can tell Kubernetes to put the pod name in an environment variable of your choice using the downward API. For example:

What is CrashLoopBackOff status for openshift pods?

由 被刻印的时光 ゝ 提交于 2019-12-08 18:48:33
问题 There is more than one example where I have seen this status from a pod running in openshift origin. In this case it was the quickstart for the cdi camel example. I was able to successfully build and run it locally (non - openshift) but when I try to deploy on my local openshift (using mvn -Pf8-local-deploy ), I get this output for that particular example (snipped for relevance) :- [vagrant@vagrant camel]$ oc get pods NAME READY STATUS RESTARTS AGE cdi-camel-z4czs 0/1 CrashLoopBackOff 4 2m

Docker maven fabric8 plugin (on Windows): building image gives incompatibility issues ?

由 允我心安 提交于 2019-12-08 13:52:43
问题 Via Maven I would like to build a Docker image from a Springboot project. I run: mvn clean package docker:build Issue: ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.21.0:build (default-cli) on project spring-boot-docker: Execution default-cli of goal io.fabric8:docker-maven-plugin:0.21.0:build failed: An API incompatibility was encountered while executing io. fabric8:docker-maven-plugin:0.21.0:build: java.lang.UnsatisfiedLinkError: unknown [ERROR] ----------------------------

Kubernetes WatchConnectionManager: Exec Failure: HTTP 403

由 纵然是瞬间 提交于 2019-12-07 18:51:57
问题 I'm experiencing Error Expected HTTP 101 response but was '403 Forbidden' After I setup a new Kubernetes cluster using Kubeadm with a single master and two workers, as I submit a pyspark sample app I encountered below ERROR message: spark-submit command spark-submit --master k8s://master-host:port \ --deploy-mode cluster --name test-pyspark \ --conf spark.kubernetes.container.image=mm45/pyspark-k8s-example:2.4.1 \ --conf spark.kubernetes.pyspark.pythonVersion=3 \ --conf spark.executor

Kubernetes WatchConnectionManager: Exec Failure: HTTP 403

由 纵然是瞬间 提交于 2019-12-06 14:18:15
I'm experiencing Error Expected HTTP 101 response but was '403 Forbidden' After I setup a new Kubernetes cluster using Kubeadm with a single master and two workers, as I submit a pyspark sample app I encountered below ERROR message: spark-submit command spark-submit --master k8s://master-host:port \ --deploy-mode cluster --name test-pyspark \ --conf spark.kubernetes.container.image=mm45/pyspark-k8s-example:2.4.1 \ --conf spark.kubernetes.pyspark.pythonVersion=3 \ --conf spark.executor.instances=1 \ --conf spark.executor.memory=1000m \ --conf spark.driver.memory=1000m \ --conf spark.executor

Can't download CXF artifacts on JBossFuse running on OpenShift

由 巧了我就是萌 提交于 2019-12-05 05:50:04
问题 I have a JBoss Fuse running on OpenShift Online and I want to deploy there a Camel-CXF application. I created a profile and attached it to a running container. When I added a feature-camel parent to this profile, the container was successfully restarted, but then I tried to add feature-cxf the container failed with the following errors: io.fabric8.agent.utils.MultiException: Error while downloading artifacts java.util.zip.ZipException: zip file is empty When I tried to add any features

利用K8S技术栈打造个人私有云（连载之：K8S资源控制）

由 微笑、不失礼 提交于 2019-12-04 13:43:45
注： 本文首发于 My 公众号 CodeSheep ，可 长按 或 扫描 下面的 小心心 来订阅 ↓ ↓ ↓ 【利用K8S技术栈打造个人私有云系列文章目录】 利用K8S技术栈打造个人私有云（连载之：初章） 利用K8S技术栈打造个人私有云（连载之：K8S集群搭建） 利用K8S技术栈打造个人私有云（连载之：K8S环境理解和练手） 利用K8S技术栈打造个人私有云（连载之：基础镜像制作与实验） 利用K8S技术栈打造个人私有云（连载之：资源控制研究） 利用K8S技术栈打造个人私有云（连载之：私有云客户端打造）（Coming Soon...） 私有云K8S资源控制原理 基于前面系列文章的详细阐述，我们已经可以手工去K8S集群的命令行下将CentOS 7.4操作系统的Docker镜像启动起来，然后用户可以通过SSH登录到CentOS容器之中进行使用。但实际使用过程中不同的用户不可能每次都手动去命令行启动一个CentOS镜像，然后用命令去查看该容器的IP地址和端口是多少，然后再通过ssh去连接。我们最好可以将Docker容器的启动、查询、删除等再封装一层，然后通过WEB页面去提供给用户操作，这才符合用户行为需求！ 由于在我们的实践中Docker容器是放在kubernetes集群中进行管理，所以这里的资源控制涉及的资源主要就是kubernetes的资源，如Pod、RC、Service等。
订阅 fabric8