10 Most Common Reasons Kubernetes Deployments Fail (Part 2)

【异常】Deployment failed: repository element was not specified in the POM inside distributionManagemen 这个错误提示表示 Maven 在尝试部署你的 tsp-web 项目到远程仓库时失败了,因为没有在项目的 POM 文件(pom.xml)中的 distributionManagement 元素内指定仓库信息,也没有在 Maven 命令中通过。这通常位于你的 Maven 安装目录的 conf 子目录下,或者在你的用户主目录下的 .m2 文件夹中。同样,替换 your-repository-id 和 http://your-repository-url/releases 为你的实际仓库 ID 和 URL。 阅读详情

Earlier this week I posted the first 5 most common reasons Kubernetes Deployments fail. Here is the remainder of the list - including some of the most frustrating!

6. Resource Quotas

Similar to resource limits, Kubernetes also allows admins to set Resource Quotas per namespace. These quotas can set soft & hard limits on resources such as number of Pods, Deployments, PersistentVolumes, CPUs, Memory, and more.

Let's see what happens when we exceed a Resource Quota. Here's our example Deployment again:


# test-quota.yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: gateway-quota
spec:
  template:
    spec:
      containers:
        - name: test-container
          image: nginx

We can create it with kubectl create -f test-quota.yaml, then inspect our Pods.


$ kubectl get pods
NAME                            READY     STATUS    RESTARTS   AGE
gateway-quota-551394438-pix5d   1/1       Running   0          16s

Looks good! Now let's scale up to 3 replicas, kubectl scale deploy/gateway-quota --replicas=3, and then inspect our Pods again.


$ kubectl get pods
NAME                            READY     STATUS    RESTARTS   AGE
gateway-quota-551394438-pix5d   1/1       Running   0          9m

Huh? Where are our pods? Let's inspect the Deployment.


$ kubectl describe deploy/gateway-quota
Name:            gateway-quota
Namespace:        fail
CreationTimestamp:    Sat, 11 Feb 2017 16:33:16 -0500
Labels:            app=gateway
Selector:        app=gateway
Replicas:        1 updated | 3 total | 1 available | 2 unavailable
StrategyType:        RollingUpdate
MinReadySeconds:    0
RollingUpdateStrategy:    1 max unavailable, 1 max surge
OldReplicaSets:        
NewReplicaSet:        gateway-quota-551394438 (1/3 replicas created)
Events:
  FirstSeen    LastSeen    Count   From                SubObjectPath   Type        Reason          Message
  ---------    --------    -----   ----                -------------   --------    ------          -------
  9m        9m      1   {deployment-controller }            Normal      ScalingReplicaSet   Scaled up replica set gateway-quota-551394438 to 1
  5m        5m      1   {deployment-controller }            Normal      ScalingReplicaSet   Scaled up replica set gateway-quota-551394438 to 3

In the last line, we can see the ReplicaSet was told to scale to 3. Let's inspect the ReplicaSet using describe to learn more.


kubectl describe replicaset gateway-quota-551394438
Name:        gateway-quota-551394438
Namespace:    fail
Image(s):    nginx
Selector:    app=gateway,pod-template-hash=551394438
Labels:        app=gateway
        pod-template-hash=551394438
Replicas:    1 current / 3 desired
Pods Status:    1 Running / 0 Waiting / 0 Succeeded / 0 Failed
No volumes.
Events:
  FirstSeen    LastSeen    Count   From                SubObjectPath   Type        Reason          Message
  ---------    --------    -----   ----                -------------   --------    ------          -------
  11m        11m     1   {replicaset-controller }            Normal      SuccessfulCreate    Created pod: gateway-quota-551394438-pix5d
  11m        30s     33  {replicaset-controller }            Warning     FailedCreate        Error creating: pods "gateway-quota-551394438-" is forbidden: exceeded quota: compute-resources, requested: pods=1, used: pods=1, limited: pods=1

Aha! Our ReplicaSet wasn't able to create any more pods due to the quota: exceeded quota: compute-resources, requested: pods=1, used: pods=1, limited: pods=1. Similar to Resource Limits, we have three options:

  1. Ask your cluster admin to increase the Quota for this namespace
  2. Delete or scale back other Deployments in this namespace
  3. Go rogue and edit the Quota

7. Insufficient Cluster Resources

Unless your cluster administrator has wired up the cluster-autoscaler, chances are that someday you will run out of CPU or Memory resources in your cluster.

That's not to say that CPU & Memory are fully utilized - just that they have been fully accounted for by the Kubernetes Scheduler. As we saw in #5, Cluster Administrators can limit the amount of CPU or memory a developer can request to be allocated to a Pod or container. Wise administrators will also set a default CPU/Memory request that will be applied if you (the developer) don't request anything.

If you do all your work in the default namespace, you probably have a default Container CPU Request of 100m and you don't even know it! Check yours by running kubectl describe ns default.

Let's say you have a Kubernetes cluster with 1 Node that has 1 CPU. Your Kubernetes cluster has 1000m of available CPU to schedule.

Ignoring other system Pods (kubectl -n kube-system get pods) for the moment, you will be able to deploy 10 Pods (with 1 container each at 100m) to your single-Node cluster.

10 Pods * (1 Container * 100m) = 1000m == Cluster CPUs

So what happens when you turn it up to 11?

Here's an example Deployment that has a CPU request of 1CPU (1000m).


# cpu-scale.yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: cpu-scale
spec:
  template:
    metadata:
      labels:
        app: cpu-scale
    spec:
      containers:
        - name: test-container
          image: nginx
          resources:
            requests:
              cpu: 1

I'm deploying this application to a Cluster that has 2 total CPUs available. In addition to my cpu-scale application, the Kubernetes internal services are consuming more CPU/Memory Requests.

So we can deploy this with kubectl create -f cpu-scale.yaml, and then inspect the Pods:


$ kubectl get pods
NAME                        READY     STATUS    RESTARTS   AGE
cpu-scale-908056305-xstti   1/1       Running   0          5m

So the first Pod was scheduled and is running. Let's see what happens when we scale up by one:


$ kubectl scale deploy/cpu-scale --replicas=2
deployment "cpu-scale" scaled
$ kubectl get pods
NAME                        READY     STATUS    RESTARTS   AGE
cpu-scale-908056305-phb4j   0/1       Pending   0          4m
cpu-scale-908056305-xstti   1/1       Running   0          5m

Uh oh. Our second Pod is stuck with a status of Pending. We can describe that second Pod for more information:


$ kubectl describe pod cpu-scale-908056305-phb4j
Name:        cpu-scale-908056305-phb4j
Namespace:    fail
Node:        gke-ctm-1-sysdig2-35e99c16-qwds/10.128.0.4
Start Time:    Sun, 12 Feb 2017 08:57:51 -0500
Labels:        app=cpu-scale
        pod-template-hash=908056305
Status:        Pending
IP:        
Controllers:    ReplicaSet/cpu-scale-908056305
[...]
Events:
  FirstSeen    LastSeen    Count   From            SubObjectPath   Type        Reason          Message
  ---------    --------    -----   ----            -------------   --------    ------          -------
  3m        3m      1   {default-scheduler }            Warning     FailedScheduling    pod (cpu-scale-908056305-phb4j) failed to fit in any node
fit failure on node (gke-ctm-1-sysdig2-35e99c16-wx0s): Insufficient cpu
fit failure on node (gke-ctm-1-sysdig2-35e99c16-tgfm): Insufficient cpu
fit failure on node (gke-ctm-1-sysdig2-35e99c16-qwds): Insufficient cpu

Alright! So the Events block tells us that the Kubernetes scheduler (default-scheduler) was unable to schedule this Pod because it failed to fit on any node. It even tells us which scalability aspect failed (Insufficient cpu) for each Node.

So how do we resolve this? Well, if you've been too eager with the size of your Requested CPU/Memory, you could reduce the request size and re-deploy. Alternatively, you could kindly ask your Cluster admin to scale up the cluster (chances are you're not the only one running into this problem).

Now, you might be thinking to yourself: "Our Kubernetes Nodes are in auto-scaling groups with our Cloud Provider. Why aren't they working?"

The answer is that your cloud provider doesn't have any insight into what the Kubernetes Scheduler is doing. Leveraging the Kubernetes cluster-autoscalerwill allow your Cluster to resize itself based on the Scheduler's requirements. If you're using Google Container Engine, the cluster-autoscaler is a Beta feature.

8. PersistentVolume fails to mount

Another common error is trying to create a Deployment that references PersistentVolumes that don't exist. Whether you're using PersistentVolumeClaims (which you should be!) or just directly accessing a PersistentDisk, the end result is very similar.

Here's our test Deployment that is trying to use a GCE PersistentDisk named my-data-disk.


# volume-test.yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: volume-test
spec:
  template:
    metadata:
      labels:
        app: volume-test
    spec:
      containers:
        - name: test-container
          image: nginx
          volumeMounts:
          - mountPath: /test
            name: test-volume
      volumes:
      - name: test-volume
        # This GCE PD must already exist (oops!)
        gcePersistentDisk:
          pdName: my-data-disk
          fsType: ext4

Let's create this Deployment, kubectl create -f volume-test.yaml and check the Pods after a few minutes.


kubectl get pods
NAME                           READY     STATUS              RESTARTS   AGE
volume-test-3922807804-33nux   0/1       ContainerCreating   0          3m

Three minutes is a long time to wait for a Container to create. Let's inspect the Pod with describe and see what's happening under the hood:


$ kubectl describe pod volume-test-3922807804-33nux
Name:        volume-test-3922807804-33nux
Namespace:    fail
Node:        gke-ctm-1-sysdig2-35e99c16-qwds/10.128.0.4
Start Time:    Sun, 12 Feb 2017 09:24:50 -0500
Labels:        app=volume-test
        pod-template-hash=3922807804
Status:        Pending
IP:        
Controllers:    ReplicaSet/volume-test-3922807804
[...]
Volumes:
  test-volume:
    Type:    GCEPersistentDisk (a Persistent Disk resource in Google Compute Engine)
    PDName:    my-data-disk
    FSType:    ext4
    Partition:    0
    ReadOnly:    false
[...]
Events:
  FirstSeen    LastSeen    Count   From                        SubObjectPath   Type        Reason      Message
  ---------    --------    -----   ----                        -------------   --------    ------      -------
  4m        4m      1   {default-scheduler }                        Normal      Scheduled   Successfully assigned volume-test-3922807804-33nux to gke-ctm-1-sysdig2-35e99c16-qwds
  1m        1m      1   {kubelet gke-ctm-1-sysdig2-35e99c16-qwds}           Warning     FailedMount Unable to mount volumes for pod "volume-test-3922807804-33nux_fail(e2180d94-f12e-11e6-bd01-42010af0012c)": timeout expired waiting for volumes to attach/mount for pod "volume-test-3922807804-33nux"/"fail". list of unattached/unmounted volumes=[test-volume]
  1m        1m      1   {kubelet gke-ctm-1-sysdig2-35e99c16-qwds}           Warning     FailedSync  Error syncing pod, skipping: timeout expired waiting for volumes to attach/mount for pod "volume-test-3922807804-33nux"/"fail". list of unattached/unmounted volumes=[test-volume]
  3m        50s     3   {controller-manager }                       Warning     FailedMount Failed to attach volume "test-volume" on node "gke-ctm-1-sysdig2-35e99c16-qwds" with: GCE persistent disk not found: diskName="my-data-disk" zone="us-central1-a"

Surprise! The Events section holds the hidden clues we were looking for. Our Pod was correctly scheduled to a Node (Successfully assigned volume-test-3922807804-33nux to gke-ctm-1-sysdig2-35e99c16-qwds), but then the Kubelet on that Node is unable to mount the expected volume, test-volume. That Volume would have been created when the PersistentDisk was attached to the Node, but, as we see further down, the controller-manager failed Failed to attach volume "test-volume" on node "gke-ctm-1-sysdig2-35e99c16-qwds" with: GCE persistent disk not found: diskName="my-data-disk" zone="us-central1-a".

This last message is pretty clear: To resolve the issue, we need to create a PersistentVolume in GKE with the name, my-data-disk in the zone, us-central1-a. Once that disk is created, the controller-manager will mount the disk and kickstart the Container creation process.

9. Validation Errors

Few things are more frustrating than watching an entire build-test-deploy job get all the way to the deploy step, only to fail due to invalid Kubernetes Spec objects.

You may have gotten error like this before:


$ kubectl create -f test-application.deploy.yaml
error: error validating "test-application.deploy.yaml": error validating data: found invalid field resources for v1.PodSpec; if you choose to ignore these errors, turn validation off with --validate=false

In this example, I tried creating the following Kubernetes Deployment:


# test-application.deploy.yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: test-app
spec:
  template:
    metadata:
      labels:
        app: test-app
    spec:
      containers:
      - image: nginx
        name: nginx
      resources:
        limits:
          cpu: 100m
          memory: 200Mi
        requests:
          cpu: 100m
          memory: 100Mi

At first glance, this YAML looks fine - but the error message proves to be helpful. The error says that it found invalid field resources for v1.PodSpec. Upon deeper inspection of the v1.PodSpec, we can see that the resources object is (incorrectly) a child of v1.PodSpec. It should be a child of v1.Container. After indenting the resources object one level, this Deployment works just fine!

In addition to looking out for indentation mistakes, another common error is a typo in an Object name (e.g. peristentVolumeClaim vs persistentVolumeClaim). That one briefly tripped up a senior engineer and I when we were in a hurry.

To help catch these errors early, I recommend adding some verification steps to your pre-commit hooks or test-phase of your build.

For example, you can:

  1. Validate your YAML with python -c 'import yaml,sys;yaml.safe_load(sys.stdin)' < test-application.deployment.yaml
  2. Validate your Kubernetes API objects using the --dry-run flag like this: kubectl create -f test-application.deploy.yaml --dry-run --validate=true

Important Note: This mechanism for validating Kubernetes Objects leverages server-side validation. This means that kubectl must have a working Kubernetes cluster to communicate with. Unfortunately, there currently is not a client-side validation option for kubectl, but there are open issues (kubernetes/kubernetes #29410 and kubernetes/kubernetes #11488 that are tracking that missing feature.

10. Container Image Not Updating

Most people I've talked to who have worked with Kubernetes have run into this problem, and it's a real kicker.

The story goes something like this:

  1. Create a Deployment using an image tag (e.g. rosskulinski/myapplication:v1)
  2. Notice that there's a bug in myapplication
  3. Build a new image and push to the same tag (rosskukulinski/myapplication:v1)
  4. Delete any myapplication Pods, watch new ones get created by the Deployment
  5. Realize that the bug is still present
  6. Repeat 3-5 until you pull your hair out

The problem relates to how Kubernetes decides whether to do a docker pullwhen starting a container in a Pod.

In the v1.Container specification there's an option called ImagePullPolicy:

Image pull policy. One of Always, Never, IfNotPresent. Defaults to Always if :latest tag is specified, or IfNotPresent otherwise.

Since we tagged our image as :v1, the default pull policy is IfNotPresent. The Kubelet already has a local copy of rosskukulinski/myapplication:v1, so it doesn't attempt to do a docker pull. When the new Pods come up, they're still using the old broken Docker image.

There are three ways to resolve this:

  1. Switch to using :latest (DO NOT DO THIS!)
  2. Specify ImagePullPolicy: Always in your Deployment.
  3. Use unique tags (e.g. based on your source control commit id)

During development or if I'm quickly prototyping something, I will specify ImagePullPolicy: Always so that I can build & push container images with the same tag.

However, in all of my production deployments I use unique tags based on the Git SHA-1 of the commit used to build that image. This makes it trivial to identify and check-out the source code that's running in production for any deployed application.


Summary

Phew! That's a lot of things to watch out for. By now, you should now be a pro at debugging, identifying, and fixing failed Kubernetes Deployments.

In general, most of the common deployment failures can be debugged using these commands:

  • kubectl describe deployment/<deployname>
  • kubectl describe replicaset/<rsname>
  • kubectl get pods
  • kubectl describe pod/<podname>
  • kubectl logs <podname> --previous

In the quest to automate myself out of a job, I created a bash script that runs anytime a CI/CD deployment fails. Helpful Kubernetes information will show up in the Jenkins/CircleCI/etc build output so that developers can quickly find any obvious problems.


I hope you have enjoyed these two posts!

How have you seen Kubernetes Deployments fail? Any other troubleshooting tips to share? Leave a comment!

PPO算法详解:基于CartPole-v1的强化学习实现 阅读详情

相关推荐

域控制器迁移后NETLOGON共享丢失的修复指南

本文详细解析了在Windows域控制器迁移后NETLOGON共享丢失的故障现象与修复方法。通过使用Dcdiag工具诊断,定位注册表键值SysVolReady异常及SCRIPTS目录缺失等核心原因,并提供了修改注册表、创建目录、重启Netlogon服务等逐步修复指南,帮助管理员快速恢复域用户登录功能,确保业务连续性。

weixin_29245767的博客 89

Kubernetes安装学习

环境:Centos 7.5            Docker 1.13.1            Kubernetes 1.5.2 官网:https://kubernetes.io/ Kubernetes架构与组件: Master包含: Etcd:集群中的主数据,存储所有资源对象及其状态,etcd的数据变更都需通过apiserver进行         Apiserver:集群控制的唯一入口,...

aryoyo的博客 658

Windows系统3D Gaussian Splatting环境搭建全攻略:从零开始到成功运行

本文详细介绍了在Windows系统上搭建3D Gaussian Splatting环境的完整流程,包括CUDA 12.6安装、Anaconda环境配置、代码获取与依赖安装等关键步骤。针对Windows平台特有的环境配置问题,提供了实用的解决方案和常见错误排查方法,帮助开发者快速实现3D Gaussian Splatting的成功运行。

weixin_30832143的博客 454

kubernetes集群问题排查

本文个人博客地址为:http://www.huweihuang.com/article/kubernetes/kubernetes-troubleshooting/本文个人博客地址为:https://huweihuang.net/article/kubernetes/kubernetes-troubleshooting/1. 查看系统Event事件kubectl describe pod &lt;...

胡伟煌的博客 2万+

嵌入式开发也玩“全家桶”?手把手教你用CLion+PyOCD调试APM32,比OpenOCD更简单

本文详细介绍了如何使用CLion和PyOCD组合进行APM32嵌入式开发,提供从环境配置到实战调试的完整指南。相比传统工具如Keil和OpenOCD,这套方案更轻量、易用,特别适合现代开发者需求,涵盖CMake配置、PyOCD调试技巧及常见问题解决。

weixin_42543046的博客 464

模仿学习算法——ATC / Diffusion Policy

最近又开始接触具身智能相关的一些工作,本文主要介绍三篇较为基础的用来做模仿学习的算法,后续有空再进一步学习分享RT系列和Pi0等文章ACT算法全称为Action Chunking with Transformers,发表于《Learning Fine-Grained Bimanual Manipulation with Low-Cost Hardware》,该论文主要内容为如何使用低成本的硬件和模仿学习算法来实的双手操作,我们主要对算法部分进行剖析ACT算法的网络结构如下图所示,使用的采用的是生成式模型VA

weixin_44580210的博客 5261

【maven】Deployment failed: repository element was not specified in the POM inside distributionManagem

原因:是deploy插件的版本是2.7,需要在项目的pom.xml文件中配置上传的仓库信息,升级到2.8后会使用setting.xml中的配置。需要把本地代码进行使用maven的上传命令时遇到的报错。

掘金者说 1万+

【功能安全】【AutoSAR】程序流监控机制

目录 一、程序流执行的常见故障 二、程序流的监控机制 1、监控功能的实现 2、三种监督机制 a、生命监测机制 b、截止时间监测机制 c、逻辑程序流监测机制 一、程序流执行的常见故障 与程序流相关的故障,在ISO26262中第六章附录D中定义如下: — 执行阻塞; — 死锁; — 活锁; — 执行时间的不正确分配; — 软件要素间的不正确同步。 二、程序流的监控机制 1、监控功能的实现 AutoSAR中对程序流的监控功能的实现主要有“看门狗”栈(Watchdog Stack).

专注汽车软件开发、AutoSAR、车载以太网、SOA、EE架构。 4521

使用 maven 部署项目到私服 nexus 出现 Deployment failed 问题的解决方法

1 问题描述一个新的工具类项目,希望部署到私服供其他项目使用。使用 maven 的 deploy 命令后,出现这个问题:[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project deniro-tools: Deployment f

读万卷书,行万里路 6909

AI预测彩票,使用chatgpt和lstm神经网络(文末附源码)

AI预测彩票,使用chatgpt和lstm神经网络(文末有彩蛋)

淘淘小窝 1万+

LIS2DH三轴加速度传感器原理图设计,已量产(加速度传感器)

最近在做一款可穿戴设备原型时,选了 LIS2DH 这款加速度计 —— 比起之前常用的 ADXL345,它在低功耗和稳定性上的优化刚好戳中了可穿戴设备 “续航 + 可靠” 的核心需求。下面结合这次画的原理图,聊聊这个小模块的硬件设计细节。

不脱发的程序猿 391

[K8S] 使用yaml文件创建deployment踩坑(新手的小坑)

虽然用过、修改过现成的yaml文件,但这个东西一次没纯手打真的不行!以下是一个非常简单且漏洞百出的yaml文件||| # WRONG example version 1 apiVersion: apps/v1 kind: Deployment metadata: name: nginx1 namespace:default spec: replicas: 3 selector: matchLabels: app: nginx2 template: meta

皮卡丘在充电 9943

C#上位机国产化适配全方案:兼容统信UOS+鲲鹏/昇腾+国产PLC,可直接交付国企项目

去年下半年,我帮天津滨海新区一家给一汽丰田做配套的汽车零部件国企,完成了3条产线、12套C#上位机的全栈国产化适配。这个项目的背景很典型,也很戳中国企客户的命门:一开始客户找了两家本地的集成商,都没搞定:第一家只会用.NET Framework,根本不知道怎么在统信UOS上跑C#;第二家勉强用.NET Core 3.1跑起来了,但和汇川国产PLC的通信丢包率高达1.2%,产线根本不敢用。我们接手后,用了2个月完成全栈适配:从Windows Server 2019迁移到统信UOS 1070d服务器版,从.NE

这里只有干货:从 Modbus 通信到 MES 对接,从 YOLO 训练到工控机部署,带你搞定工业软件开发全流程。 500

Deployment failed: repository element was not specified in the POM inside....(已解决)

Deployment failed: repository element was not specified in the POM inside…(已解决) 都搜到这里了你可以不用看其他文章了 出现这个原因无非是想在本地的pom文件配置好之后,执行deploy命令,可以将maven所打的jar包上传到远程的repository,便于其他开发者和工程共享。但是!!!!!!你自己本地都没有!!!distributionManagement你怎么上传到私服啊!!!!!,因此解决方案 在你自己的项目下的pom文

2万+

Statistics and Machine Learning Toolbox

Statistics and Machine Learning Toolbox(带书签),MATLAB统计学习工具

android 蓝牙通讯demo

android 下蓝牙通讯demo,实现了发现蓝牙,使能蓝牙,通过蓝牙发送消息。

Deployment failed: repository element was not specified in the POM inside distributionManagement ele

Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter 在使用maven的上传命令时遇到的报错

zx1323的博客 2万+

Outlook Express 6 (OE6) for Win7/Win8/Win10

英文版 Outlook Express6.0, 兼容Win7/Win10/WinXP,解压就可用。

error: error validating “deployment. yaml“: error validating data: apiVersion not set; if you choose

错误:验证“部署”错误。yaml":错误验证数据:apiVersion未设置;如果您选择忽略这些错误,请使用——validate=false关闭验证 有可能是yuml文件书写错误,部署时最好复制粘贴,别手敲。 我这次的错误原因是在于没有按a进入编辑模式,直接粘贴,导致内容缺失。所以报错无法创建。 重新修改文件内容后成功创建。 ...

weixin_45387943的博客 4748

锂电池充电器电路设计 里面有电路

锂电池充电器电路设计 里面有电路 3.7V升压到5V电路设计。

myeclipse出现Deployment failed错误

错误描述: Cannot find the fileC:\Users\sss\Desktop\zzt- maven\target\classes\com\mingxu\ZZTrainStationExam\java\controller\DepartmentController.class in the file system. Make sure the file exists and try

博客写得好,技术好,才是真的好 7244

Deployment failed because of an internal error: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE]

Happened to me today and left me confused. The thing is that I: 1) Installed APK of my App from different source. 2) Then I wanted to install it from Xamarin Studio. 3) Previous App got uninstalled

zl325118的博客 1457

K8S创建Deployment报错(汇总)

K8S创建Deployment报错误

cuibin1991的专栏 2410

vsphere部署模板OVF时报错Deployment Failed: File ds:///vmfs的问题解决

根据官方文档《安装 VMware Tools 后在 vCenter Server 5.1/5.5 上部署 OVF 失败 (2034422)》的案例描述执行以下操作。文档查看不仔细,官方资料里描述了,当你修改完了OVF文件之后,部署会报错。打开导出的虚拟机文件夹,共有3个内容文件。记录下更新后的ovf文件SHA1的值,并修改.mf文件里对应的值。据度娘解答,原因可能是导出虚拟机之前,没有清空虚拟机光驱内容。今天要恢复一个之前备份的虚拟机,测试部署OVF时报错如下图。要修改的内容如下图红框里的内容。

huiyangxu blog 898

K8S报错error validating data: ValidationError(Deployment.spec): missing required field selector

报错如下 这是我在执行 deployment控制器的Pod副本时出现的报错,报错意思: 部署验证错误,在deploymentspec模块中必须指定 selector参数。 原YAML文件 在 Deployment.spec 模块中,只指定了 replicas 副本数量,还需要指定副本标签与 Deployment控制器进行匹配 apiVersion: apps/v1 #Api接口版本 kind: Deployment #定义控制器 metadata: name: nginx-

北海牧野 3万+

k8s技术遇到的问题3--error: error validating “k8s_pod.yml“: error validating data: found invalid field....

[root@master test]# kubectl create -f k8s_pod.yml error: error validating “k8s_pod.yml”: error validating data: found invalid field template for v1.Pod; if you choose to ignore these errors, turn validation off with --validate=false 解决方法: 检查配置文件 1.查看自己有没有单

weixin_44736359的博客 1万+

根据实践学习K8S--7.使用Deployment进行不停机升级和回滚以及手动扩缩容

在现网情况下,业务升级常常需要停机,下面我们使用Deployment来进行不停机升级和回滚. 1.先使用创建多个nginx的pod [root@node-1 pod]# cat nginx_deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: name: nginx-deployment spec: replicas...

weixin_43354959的博客 1100

k8s不能挂载ceph块存储

我是参考 Tony Bai 博客进行k8s挂载ceph的存储,但是发现最终pod的状态一直是ContainerCreating一、环境说明: Tony Bai 是把k8s 和 ceph都部署在那两台虚拟机上 我的环境是k8s集群和ceph存储集群分别部署在不同机器上的 ceph存储集群环境部署可以参考Tony Bai的,或者网上找很多教程,我这里只是记录k8s挂载到ceph块存储所遇到的问题。二、配

每天的表现,未来的必然! 5543

Kubernetes 部署失败的 10 个最普遍原因

[原文]在过去的两年间,我和许多团队合作,一起用 Kubernetes 来部署他们的应用。要想让开发者跟上 Kubernetes 术语的发展速度是很困难的,因此当部署失败的时候,我总是被要求指出哪个地方错了。和客户一起工作,我的一个主要目标是自动化,尽可能把自己从繁琐的定位工作中解放出来。因此我努力给开发者必要的工具,使得他们自己就能定位部署失败的原因。我总结了 Kubernetes 部署失败的最...

weixin_30398227的博客 6433

Maven常见异常及解决方法(本篇更新至16-4-12)

本篇文章记录了老猫在学习整合Maven和SSH过程中遇到的问题,有的问题能够解决,有的问题还不能解决。方法不一定适合所有的环境,但绝对是本人常遇到的常见异常,在这里做一个笔记和记录,也分享给大家,希望大家多多给出见解! 如果有不同的见解,请按照编号写出自己的见解吧,老猫愿闻其详!

机智猫 6万+
上一篇: 集中化管理平台 — Ansible 详解
下一篇: 【ValueError: math domain error】
hxpjava1
博客等级 码龄19年 1365粉丝 511原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值