Camel K 和 Amazon EKS（弹性 Kubernetes 服务）

大佬教程收集整理的这篇文章主要介绍了Camel K 和 Amazon EKS（弹性 Kubernetes 服务），大佬教程大佬觉得挺不错的，现在分享给大家，也给大家做个参考。

如何解决Camel K 和 Amazon EKS（弹性 Kubernetes 服务）？

开发过程中遇到Camel K 和 Amazon EKS（弹性 Kubernetes 服务）的问题如何解决？下面主要结合日常开发的经验，给出你关于Camel K 和 Amazon EKS（弹性 Kubernetes 服务）的解决方法建议，希望对你解决Camel K 和 Amazon EKS（弹性 Kubernetes 服务）有所启发或帮助；

我正在尝试部署一个简单的 camel-k 配置并使其与 Amazon EKS 配合使用。 我做了什么：

1. 基于 Amazon EKS 创建了一个新的 Kubernetes 集群 enter image description here
2. 使用命令安装 Camel-K

kamel install --registry docker.io --organization user_iD --registry-secret pass

enter image description here 在此之后，我有一个骆驼-k 活动吊舱 enter image description here 3. 尝试运行跟随示例集成

// camel-k: language=java

    import org.apache.camel.builder.RouteBuilder;
    public class Demo extends RouteBuilder {
      @OverrIDe
      public voID configure() throws Exception {
          // Write your routes here,for example:
          from("timer:java?period=1000")
            .routEID("java")
            .setbody()
              .simple("Hello Camel K from ${routEID}")
            .to("log:info");
      }
    }

使用命令

kamel run Demo.java --dev

我在这个命令之后有下一个输出：

Progress: integration "demo" in phase Initialization
Progress: integration "demo" in phase Building Kit
Condition "IntegrationPlatformAvailable" is "True" for Integration demo: default/camel-k
Integration demo in phase "Initialization"
Integration demo in phase "Building Kit"
Condition "IntegrationKitAvailable" is "false" for Integration demo: creaTing a new integration kit
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Integration Kit) changed phase to "Build submitted"
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "scheduling"
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Pending"
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Running"
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Integration Kit) changed phase to "Build Running"
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Failed"
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Initialization" (recovery 1 of 5)
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "scheduling" (recovery 1 of 5)
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Pending" (recovery 1 of 5)
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Running" (recovery 1 of 5)
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Failed" (recovery 1 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Initialization" (recovery 2 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "scheduling" (recovery 2 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Pending" (recovery 2 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Running" (recovery 2 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Failed" (recovery 2 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Initialization" (recovery 3 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "scheduling" (recovery 3 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Pending" (recovery 3 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Running" (recovery 3 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Failed" (recovery 3 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Initialization" (recovery 4 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "scheduling" (recovery 4 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Pending" (recovery 4 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Running" (recovery 4 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Failed" (recovery 4 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Initialization" (recovery 5 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "scheduling" (recovery 5 of 5)
(combined from similar events): Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Build) changed phase to "Failed" (recovery 5 of 5)
Integration demo subresource kit-c23tllgnm1jafvoms1t0 (Integration Kit) changed phase to "Error"
Progress: integration "demo" in phase Error
Error: integration "demo" deployment Failed

我得到了camel pod (camel-k-operator-ID) 日志，但是我在日志中找不到任何可以帮助我理解此错误真正问题的信息。 有人可以帮助我如何获取发生错误的详细信息吗？

主要问题是否可以将 Camel-K 与 Amazon Elastic Kubernetes service 一起使用？ 我没有在官方文档中找到任何信息。

解决方法

大佬总结

以上是大佬教程为你收集整理的Camel K 和 Amazon EKS（弹性 Kubernetes 服务）全部内容，希望文章能够帮你解决Camel K 和 Amazon EKS（弹性 Kubernetes 服务）所遇到的程序开发问题。

如果觉得大佬教程网站内容还不错，欢迎将大佬教程推荐给程序员好友。

本图文内容来源于网友网络收集整理提供，作为学习参考使用，版权属于原作者。
如您有任何意见或建议可联系处理。小编QQ：384754419，请注明来意。