Abundancemarble MCP

MCP运维云端

提供方 godfirstjohnjames-gmail-com

运维云端 未标注 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorWindsurf

基于NGINX的Kubernetes Ingress控制器,提供反向代理和负载均衡功能。

一句话选型结论

按资料字段整理

Abundancemarble MCP 属于运维云端类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 1 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

Kubernetes本地部署Ingress控制器负载均衡反向代理云原生

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Abundancemarble MCP当前 未标注 未标注 未标注 无 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方godfirstjohnjames-gmail-com上游标注的维护方 godfirstjohnjames-gmail-com
分类运维云端本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

54.5 KB
来自项目仓库与上游目录的原文,未做删改

ingress-nginx

ingress-nginx Ingress controller for Kubernetes using NGINX as a reverse proxy and load balancer

To use, add ingressClassName: nginx spec field or the kubernetes.io/ingress.class: nginx annotation to your Ingress resources.

This chart bootstraps an ingress-nginx deployment on a Kubernetes cluster using the Helm package manager.

Requirements

Kubernetes: >=1.21.0-0

Get Repo Info```console

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update


## Install Chart

**Important:** only helm3 is supported```console
helm install [RELEASE_NAME] ingress-nginx/ingress-nginx

The command deploys ingress-nginx on the Kubernetes cluster in the default configuration.

See configuration below.

See helm install for command documentation.

Uninstall Chart```console

helm uninstall [RELEASE_NAME]


This removes all the Kubernetes components associated with the chart and deletes the release.

_See helm uninstall for command documentation._

## Upgrading Chart```console
helm upgrade [RELEASE_NAME] [CHART] --install

See helm upgrade for command documentation.

Migrating from stable/nginx-ingress

There are two main ways to migrate a release from stable/nginx-ingress to ingress-nginx/ingress-nginx chart:

  1. For Nginx Ingress controllers used for non-critical services, the easiest method is to uninstall the old release and install the new one
  2. For critical services in production that require zero-downtime, you will want to:
    1. Install a second Ingress controller
    2. Redirect your DNS traffic from the old controller to the new controller
    3. Log traffic from both controllers during this changeover
    4. Uninstall the old controller once traffic has fully drained from it

Note that there are some different and upgraded configurations between the two charts, described by Rimas Mocevicius from JFrog in the "Upgrading to ingress-nginx Helm chart" section of Migrating from Helm chart nginx-ingress to ingress-nginx. As the ingress-nginx/ingress-nginx chart continues to update, you will want to check current differences by running helm configuration commands on both charts.

Configuration

See Customizing the Chart Before Installing. To see all configurable options with detailed comments, visit the chart's values.yaml, or run these configuration commands:```console
helm show values ingress-nginx/ingress-nginx


### PodDisruptionBudget

Note that the PodDisruptionBudget resource will only be defined if the replicaCount is greater than one,
else it would make it impossible to evacuate a node. See gh issue #7127 for more info.

### Prometheus Metrics

The Ingress-Nginx Controller can export Prometheus metrics, by setting `controller.metrics.enabled` to `true`.

You can add Prometheus annotations to the metrics service using `controller.metrics.service.annotations`.
Alternatively, if you use the Prometheus Operator, you can enable ServiceMonitor creation using `controller.metrics.serviceMonitor.enabled`. And set `controller.metrics.serviceMonitor.additionalLabels.release="prometheus"`. "release=prometheus" should match the label configured in the prometheus servicemonitor ( see `kubectl get servicemonitor prometheus-kube-prom-prometheus -oyaml -n prometheus`)

### ingress-nginx nginx\_status page/stats server

Previous versions of this chart had a `controller.stats.*` configuration block, which is now obsolete due to the following changes in Ingress-Nginx Controller:

- In 0.16.1, the vts (virtual host traffic status) dashboard was removed
- In 0.23.0, the status page at port 18080 is now a unix socket webserver only available at localhost.
  You can use `curl --unix-socket /tmp/nginx-status-server.sock http://localhost/nginx_status` inside the controller container to access it locally, or use the snippet from nginx-ingress changelog to re-enable the http server

### ExternalDNS Service Configuration

Add an ExternalDNS annotation to the LoadBalancer service:```yaml
controller:
  service:
    annotations:
      external-dns.alpha.kubernetes.io/hostname: kubernetes-example.com.

AWS L7 ELB with SSL Termination

Annotate the controller as shown in the nginx-ingress l7 patch:```yaml
controller:
service:
targetPorts:
http: http
https: http
annotations:
service.beta.kubernetes.io/aws-load-balancer-ssl-cert: arn:aws:acm:XX-XXXX-X:XXXXXXXXX:certificate/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXX
service.beta.kubernetes.io/aws-load-balancer-backend-protocol: "http"
service.beta.kubernetes.io/aws-load-balancer-ssl-ports: "https"
service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: '3600'


### Additional Internal Load Balancer

This setup is useful when you need both external and internal load balancers but don't want to have multiple ingress controllers and multiple ingress objects per application.

By default, the ingress object will point to the external load balancer address, but if correctly configured, you can make use of the internal one if the URL you are looking up resolves to the internal load balancer's URL.

You'll need to set both the following values:

`controller.service.internal.enabled`
`controller.service.internal.annotations`

If one of them is missing the internal load balancer will not be deployed. Example you may have `controller.service.internal.enabled=true` but no annotations set, in this case no action will be taken.

`controller.service.internal.annotations` varies with the cloud service you're using.

Example for AWS:```yaml
controller:
  service:
    internal:
      enabled: true
      annotations:
        # Create internal NLB
        service.beta.kubernetes.io/aws-load-balancer-scheme: "internal"
        # Create internal ELB(Deprecated)
        # service.beta.kubernetes.io/aws-load-balancer-internal: "true"
        # Any other annotation can be declared here.

Example for GCE:```yaml
controller:
service:
internal:
enabled: true
annotations:
# Create internal LB. More information: https://cloud.google.com/kubernetes-engine/docs/how-to/internal-load-balancing
# For GKE versions 1.17 and later
networking.gke.io/load-balancer-type: "Internal"
# For earlier versions
# cloud.google.com/load-balancer-type: "Internal"

    # Any other annotation can be declared here.

Example for Azure:```yaml
controller:
  service:
      annotations:
        # Create internal LB
        service.beta.kubernetes.io/azure-load-balancer-internal: "true"
        # Any other annotation can be declared here.

Example for Oracle Cloud Infrastructure:```yaml
controller:
service:
annotations:
# Create internal LB
service.beta.kubernetes.io/oci-load-balancer-internal: "true"
# Any other annotation can be declared here.


The load balancer annotations of more cloud service providers can be found: Internal load balancer.

An use case for this scenario is having a split-view DNS setup where the public zone CNAME records point to the external balancer URL while the private zone CNAME records point to the internal balancer URL. This way, you only need one ingress kubernetes object.

Optionally you can set `controller.service.loadBalancerIP` if you need a static IP for the resulting `LoadBalancer`.

### Ingress Admission Webhooks

With nginx-ingress-controller version 0.25+, the Ingress-Nginx Controller pod exposes an endpoint that will integrate with the `validatingwebhookconfiguration` Kubernetes feature to prevent bad ingress from being added to the cluster.
**This feature is enabled by default since 0.31.0.**

With nginx-ingress-controller in 0.25.* work only with kubernetes 1.14+, 0.26 fix this issue

#### How the Chart Configures the Hooks
A validating and configuration requires the endpoint to which the request is sent to use TLS. It is possible to set up custom certificates to do this, but in most cases, a self-signed certificate is enough. The setup of this component requires some more complex orchestration when using helm. The steps are created to be idempotent and to allow turning the feature on and off without running into helm quirks.

1. A pre-install hook provisions a certificate into the same namespace using a format compatible with provisioning using end user certificates. If the certificate already exists, the hook exits.
2. The Ingress-Nginx Controller pod is configured to use a TLS proxy container, which will load that certificate.
3. Validating and Mutating webhook configurations are created in the cluster.
4. A post-install hook reads the CA from the secret created by step 1 and patches the Validating and Mutating webhook configurations. This process will allow a custom CA provisioned by some other process to also be patched into the webhook configurations. The chosen failure policy is also patched into the webhook configurations

#### Alternatives
It should be possible to use cert-manager/cert-manager if a more complete solution is required.

You can enable automatic self-signed TLS certificate provisioning via cert-manager by setting the `controller.admissionWebhooks.certManager.enabled` value to true.

Please ensure that cert-manager is correctly installed and configured.

### Helm Error When Upgrading: spec.clusterIP: Invalid value: ""

If you are upgrading this chart from a version between 0.31.0 and 1.2.2 then you may get an error like this:```console
Error: UPGRADE FAILED: Service "?????-controller" is invalid: spec.clusterIP: Invalid value: "": field is immutable

Detail of how and why are in this issue but to resolve this you can set xxxx.service.omitClusterIP to true where xxxx is the service referenced in the error.

As of version 1.26.0 of this chart, by simply not providing any clusterIP value, invalid: spec.clusterIP: Invalid value: "": field is immutable will no longer occur since clusterIP: "" will not be rendered.

Pod Security Admission

You can use Pod Security Admission by applying labels to the ingress-nginx namespace as instructed by the documentation.

Example:yaml apiVersion: v1 kind: Namespace metadata: name: ingress-nginx labels: kubernetes.io/metadata.name: ingress-nginx name: ingress-nginx pod-security.kubernetes.io/enforce: restricted pod-security.kubernetes.io/enforce-version: v1.31

Values

Key · Type · Default · Description
commonLabels · object · {}
controller.addHeaders · object · {} · Will add custom headers before sending response traffic to the client according to: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#add-headers
controller.admissionWebhooks.annotations · object · {}
controller.admissionWebhooks.certManager.admissionCert.duration · string · ""
controller.admissionWebhooks.certManager.admissionCert.revisionHistoryLimit · int · 0 · Revision history limit of the webhook certificate. Ref.: https://cert-manager.io/docs/reference/api-docs/#cert-manager.io/v1.CertificateSpec
controller.admissionWebhooks.certManager.enabled · bool · false
controller.admissionWebhooks.certManager.rootCert.duration · string · ""
controller.admissionWebhooks.certManager.rootCert.revisionHistoryLimit · int · 0 · Revision history limit of the root certificate. Ref.: https://cert-manager.io/docs/reference/api-docs/#cert-manager.io/v1.CertificateSpec
controller.admissionWebhooks.certificate · string · "/usr/local/certificates/cert"
controller.admissionWebhooks.createSecretJob.activeDeadlineSeconds · int · 0 · Deadline in seconds for the job to complete. Must be greater than 0 to enforce. If unset or 0, no deadline is enforced.
controller.admissionWebhooks.createSecretJob.name · string · "create"
controller.admissionWebhooks.createSecretJob.resources · object · {}
controller.admissionWebhooks.createSecretJob.securityContext · object · {"allowPrivilegeEscalation":false,"capabilities":{"drop":["ALL"]},"readOnlyRootFilesystem":true,"runAsGroup":65532,"runAsNonRoot":true,"runAsUser":65532,"seccompProfile":{"type":"RuntimeDefault"}} · Security context for secret creation containers
controller.admissionWebhooks.createSecretJob.volumeMounts · list · [] · Volume mounts for secret creation containers
controller.admissionWebhooks.createSecretJob.volumes · list · [] · Volumes for secret creation pod
controller.admissionWebhooks.enabled · bool · true
controller.admissionWebhooks.extraEnvs · list · [] · Additional environment variables to set
controller.admissionWebhooks.failurePolicy · string · "Fail" · Admission Webhook failure policy to use
controller.admissionWebhooks.key · string · "/usr/local/certificates/key"
controller.admissionWebhooks.labels · object · {} · Labels to be added to admission webhooks
controller.admissionWebhooks.name · string · "admission"
controller.admissionWebhooks.namespaceSelector · object · {}
controller.admissionWebhooks.objectSelector · object · {}
controller.admissionWebhooks.patch.enabled · bool · true
controller.admissionWebhooks.patch.image.digest · string · "sha256:b28e0688be7d1e15fe385053bd4c6b631bc7708c9220632de1b95867e5e7da11"
controller.admissionWebhooks.patch.image.image · string · "ingress-nginx/kube-webhook-certgen"
controller.admissionWebhooks.patch.image.pullPolicy · string · "IfNotPresent"
controller.admissionWebhooks.patch.image.tag · string · "v1.6.6"
controller.admissionWebhooks.patch.labels · object · {} · Labels to be added to patch job resources
controller.admissionWebhooks.patch.networkPolicy.enabled · bool · false · Enable 'networkPolicy' or not
controller.admissionWebhooks.patch.nodeSelector."kubernetes.io/os" · string · "linux"
controller.admissionWebhooks.patch.podAnnotations · object · {}
controller.admissionWebhooks.patch.priorityClassName · string · "" · Provide a priority class name to the webhook patching job #
controller.admissionWebhooks.patch.rbac · object · {"create":true} · Admission webhook patch job RBAC
controller.admissionWebhooks.patch.rbac.create · bool · true · Create RBAC or not
controller.admissionWebhooks.patch.runtimeClassName · string · "" · Instruct the kubelet to use the named RuntimeClass to run the pod
controller.admissionWebhooks.patch.securityContext · object · {} · Security context for secret creation & webhook patch pods
controller.admissionWebhooks.patch.serviceAccount · object · {"automountServiceAccountToken":true,"create":true,"name":""} · Admission webhook patch job service account
controller.admissionWebhooks.patch.serviceAccount.automountServiceAccountToken · bool · true · Auto-mount service account token or not
controller.admissionWebhooks.patch.serviceAccount.create · bool · true · Create a service account or not
controller.admissionWebhooks.patch.serviceAccount.name · string · "" · Custom service account name
controller.admissionWebhooks.patch.tolerations · list · []
controller.admissionWebhooks.patchWebhookJob.activeDeadlineSeconds · int · 0 · Deadline in seconds for the job to complete. Must be greater than 0 to enforce. If unset or 0, no deadline is enforced.
controller.admissionWebhooks.patchWebhookJob.name · string · "patch"
controller.admissionWebhooks.patchWebhookJob.resources · object · {}
controller.admissionWebhooks.patchWebhookJob.securityContext · object · {"allowPrivilegeEscalation":false,"capabilities":{"drop":["ALL"]},"readOnlyRootFilesystem":true,"runAsGroup":65532,"runAsNonRoot":true,"runAsUser":65532,"seccompProfile":{"type":"RuntimeDefault"}} · Security context for webhook patch containers
controller.admissionWebhooks.patchWebhookJob.volumeMounts · list · [] · Volume mounts for webhook patch containers
controller.admissionWebhooks.patchWebhookJob.volumes · list · [] · Volumes for webhook patch pod
controller.admissionWebhooks.port · int · 8443
controller.admissionWebhooks.service.annotations · object · {}
controller.admissionWebhooks.service.externalIPs · list · []
controller.admissionWebhooks.service.loadBalancerSourceRanges · list · []
controller.admissionWebhooks.service.servicePort · int · 443
controller.admissionWebhooks.service.type · string · "ClusterIP"
controller.affinity · object · {} · Affinity and anti-affinity rules for server scheduling to nodes # Ref: https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#affinity-and-anti-affinity #
controller.allowSnippetAnnotations · bool · false · This configuration defines if Ingress Controller should allow users to set their own *-snippet annotations, otherwise this is forbidden / dropped when users add those annotations. Global snippets in ConfigMap are still respected
controller.annotations · object · {} · Annotations to be added to the controller Deployment or DaemonSet #
controller.autoscaling.annotations · object · {}
controller.autoscaling.behavior · object · {}
controller.autoscaling.enabled · bool · false
controller.autoscaling.maxReplicas · int · 11
controller.autoscaling.minReplicas · int · 1
controller.autoscaling.targetCPUUtilizationPercentage · int · 50
controller.autoscaling.targetMemoryUtilizationPercentage · int · 50
controller.autoscalingTemplate · list · []
controller.config · object · {} · Global configuration passed to the ConfigMap consumed by the controller. Values may contain Helm templates. Ref.: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/
controller.configAnnotations · object · {} · Annotations to be added to the controller config configuration configmap.
controller.configMapNamespace · string · "" · Allows customization of the configmap / nginx-configmap namespace; defaults to $(POD_NAMESPACE)
controller.containerName · string · "controller" · Configures the controller container name
controller.containerPort · object · {"http":80,"https":443} · Configures the ports that the nginx-controller listens on
controller.containerSecurityContext · object · {} · Security context for controller containers
controller.customTemplate.configMapKey · string · ""
controller.customTemplate.configMapName · string · ""
controller.disableLeaderElection · bool · false · This configuration disable Nginx Controller Leader Election
controller.dnsConfig · object · {} · Optionally customize the pod dnsConfig.
controller.dnsPolicy · string · "ClusterFirst" · Optionally change this to ClusterFirstWithHostNet in case you have 'hostNetwork: true'. By default, while using host network, name resolution uses the host's DNS. If you wish nginx-controller to keep resolving names inside the k8s network, use ClusterFirstWithHostNet.
controller.electionID · string · "" · Election ID to use for status update, by default it uses the controller name combined with a suffix of 'leader'
controller.electionTTL · string · "" · Duration a leader election is valid before it's getting re-elected, e.g. 15s, 10m or 1h. (Default: 30s)
controller.enableAnnotationValidations · bool · true
controller.enableMimalloc · bool · true · Enable mimalloc as a drop-in replacement for malloc. # ref: https://github.com/microsoft/mimalloc #
controller.enableTopologyAwareRouting · bool · false · This configuration enables Topology Aware Routing feature, used together with service annotation service.kubernetes.io/topology-mode="auto" Defaults to false
controller.extraArgs · object · {} · Additional command line arguments to pass to Ingress-Nginx Controller E.g. to specify the default SSL certificate you can use
controller.extraContainers · list · [] · Additional containers to be added to the controller pod. See https://github.com/lemonldap-ng-controller/lemonldap-ng-controller as example.
controller.extraEnvs · list · [] · Additional environment variables to set
controller.extraInitContainers · list · [] · Containers, which are run before the app containers are started. Values may contain Helm templates.
controller.extraModules · list · [] · Modules, which are mounted into the core nginx image.
controller.extraVolumeMounts · list · [] · Additional volumeMounts to the controller main container.
controller.extraVolumes · list · [] · Additional volumes to the controller pod.
controller.healthCheckHost · string · "" · Address to bind the health check endpoint. It is better to set this option to the internal node address if the Ingress-Nginx Controller is running in the hostNetwork: true mode.
controller.healthCheckPath · string · "/healthz" · Path of the health check endpoint. All requests received on the port defined by the healthz-port parameter are forwarded internally to this path.
controller.hostAliases · list · [] · Optionally customize the pod hostAliases.
controller.hostNetwork · bool · false · Required for use with CNI based kubernetes installations (such as ones set up by kubeadm), since CNI and hostport don't mix yet. Can be deprecated once https://github.com/kubernetes/kubernetes/issues/23920 is merged
controller.hostPort.enabled · bool · false · Enable 'hostPort' or not
controller.hostPort.ports.http · int · 80 · 'hostPort' http port
controller.hostPort.ports.https · int · 443 · 'hostPort' https port
controller.hostname · object · {} · Optionally customize the pod hostname.
controller.image.allowPrivilegeEscalation · bool · false
controller.image.chroot · bool · false
controller.image.digest · string · "sha256:fb3e5c0bdff6a498dd5192b11a09ace0739baa9fe6ba519bf5b22425871ce490"
controller.image.digestChroot · string · "sha256:c46f14a73fb06f2ac2d85d2e576a39563c874fa182076c1ced8b44e24247a80b"
controller.image.image · string · "ingress-nginx/controller"
controller.image.pullPolicy · string · "IfNotPresent"
controller.image.readOnlyRootFilesystem · bool · false
controller.image.runAsGroup · int · 82 · This value must not be changed using the official image. uid=101(www-data) gid=82(www-data) groups=82(www-data)
controller.image.runAsNonRoot · bool · true
controller.image.runAsUser · int · 101 · This value must not be changed using the official image. uid=101(www-data) gid=82(www-data) groups=82(www-data)
controller.image.seccompProfile.type · string · "RuntimeDefault"
controller.image.tag · string · "v1.14.2"
controller.ingressClass · string · "nginx" · For backwards compatibility with ingress.class annotation, use ingressClass. Algorithm is as follows, first ingressClassName is considered, if not present, controller looks for ingress.class annotation
controller.ingressClassByName · bool · false · Process IngressClass per name (additionally as per spec.controller).
controller.ingressClassResource · object · {"aliases":[],"annotations":{},"controllerValue":"k8s.io/ingress-nginx","default":false,"enabled":true,"name":"nginx","parameters":{}} · This section refers to the creation of the IngressClass resource. IngressClasses are immutable and cannot be changed after creation. We do not support namespaced IngressClasses, yet, so a ClusterRole and a ClusterRoleBinding is required.
controller.ingressClassResource.aliases · list · [] · Aliases of this IngressClass. Creates copies with identical settings but the respective alias as name. Useful for development environments with only one Ingress Controller but production-like Ingress resources. default gets enabled on the original IngressClass only.
controller.ingressClassResource.annotations · object · {} · Annotations to be added to the IngressClass resource.
controller.ingressClassResource.controllerValue · string · "k8s.io/ingress-nginx" · Controller of the IngressClass. An Ingress Controller looks for IngressClasses it should reconcile by this value. This value is also being set as the --controller-class argument of this Ingress Controller. Ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class
controller.ingressClassResource.default · bool · false · If true, Ingresses without ingressClassName get assigned to this IngressClass on creation. Ingress creation gets rejected if there are multiple default IngressClasses. Ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#default-ingress-class
controller.ingressClassResource.enabled · bool · true · Create the IngressClass or not
controller.ingressClassResource.name · string · "nginx" · Name of the IngressClass
controller.ingressClassResource.parameters · object · {} · A link to a custom resource containing additional configuration for the controller. This is optional if the controller consuming this IngressClass does not require additional parameters. Ref: https://kubernetes.io/docs/concepts/services-networking/ingress/#ingress-class
controller.keda.apiVersion · string · "keda.sh/v1alpha1"
controller.keda.behavior · object · {}
controller.keda.cooldownPeriod · int · 300
controller.keda.enabled · bool · false
controller.keda.maxReplicas · int · 11
controller.keda.minReplicas · int · 1
controller.keda.pollingInterval · int · 30
controller.keda.restoreToOriginalReplicaCount · bool · false
controller.keda.scaledObject.annotations · object · {}
controller.keda.triggers · list · []
controller.kind · string · "Deployment" · Use a DaemonSet or Deployment
controller.labels · object · {} · Labels to be added to the controller Deployment or DaemonSet and other resources that do not have option to specify labels #
controller.lifecycle · object · {"preStop":{"exec":{"command":["/wait-shutdown"]}}} · Improve connection draining when ingress controller pod is deleted using a lifecycle hook: With this new hook, we increased the default terminationGracePeriodSeconds from 30 seconds to 300, allowing the draining of connections up to five minutes. If the active connections end before that, the pod will terminate gracefully at that time. To effectively take advantage of this feature, the Configmap feature worker-shutdown-timeout new value is 240s instead of 10s. #
controller.livenessProbe.failureThreshold · int · 5
controller.livenessProbe.httpGet.path · string · "/healthz"
controller.livenessProbe.httpGet.port · int · 10254
controller.livenessProbe.httpGet.scheme · string · "HTTP"
controller.livenessProbe.initialDelaySeconds · int · 10
controller.livenessProbe.periodSeconds · int · 10
controller.livenessProbe.successThreshold · int · 1
controller.livenessProbe.timeoutSeconds · int · 1
controller.maxmindLicenseKey · string · "" · Maxmind license key to download GeoLite2 Databases. # https://blog.maxmind.com/2019/12/significant-changes-to-accessing-and-using-geolite2-databases/
controller.metrics.enabled · bool · false
controller.metrics.port · int · 10254
controller.metrics.portName · string · "metrics"
controller.metrics.prometheusRule.additionalLabels · object · {}
controller.metrics.prometheusRule.annotations · object · {} · Annotations to be added to the PrometheusRule.
controller.metrics.prometheusRule.enabled · bool · false
controller.metrics.prometheusRule.rules · list · []
controller.metrics.service.annotations · object · {}
controller.metrics.service.enabled · bool · true · Enable the metrics service or not.
controller.metrics.service.externalIPs · list · [] · List of IP addresses at which the stats-exporter service is available # Ref: https://kubernetes.io/docs/concepts/services-networking/service/#external-ips #
controller.metrics.service.labels · object · {} · Labels to be added to the metrics service resource
controller.metrics.service.loadBalancerSourceRanges · list · []
controller.metrics.service.servicePort · int · 10254
controller.metrics.service.type · string · "ClusterIP"
controller.metrics.serviceMonitor.additionalLabels · object · {}
controller.metrics.serviceMonitor.annotations · object · {} · Annotations to be added to the ServiceMonitor.
controller.metrics.serviceMonitor.enabled · bool · false
controller.metrics.serviceMonitor.labelLimit · int · 0 · Per-scrape limit on number of labels that will be accepted for a sample.
controller.metrics.serviceMonitor.labelNameLengthLimit · int · 0 · Per-scrape limit on length of labels name that will be accepted for a sample.
controller.metrics.serviceMonitor.labelValueLengthLimit · int · 0 · Per-scrape limit on length of labels value that will be accepted for a sample.
controller.metrics.serviceMonitor.metricRelabelings · list · []
controller.metrics.serviceMonitor.namespace · string · ""
controller.metrics.serviceMonitor.namespaceSelector · object · {}
controller.metrics.serviceMonitor.relabelings · list · []
controller.metrics.serviceMonitor.sampleLimit · int · 0 · Defines a per-scrape limit on the number of scraped samples that will be accepted.
controller.metrics.serviceMonitor.scrapeInterval · string · "30s"
controller.metrics.serviceMonitor.scrapeTimeout · string · "" · Timeout after which the scrape is ended. Not being set if empty and therefore defaults to the global Prometheus scrape timeout.
controller.metrics.serviceMonitor.targetLabels · list · []
controller.metrics.serviceMonitor.targetLimit · int · 0 · Defines a limit on the number of scraped targets that will be accepted.
controller.minAvailable · int · 1 · Minimum available pods set in PodDisruptionBudget. Define either 'minAvailable' or 'maxUnavailable', never both.
controller.minReadySeconds · int · 0 · minReadySeconds to avoid killing pods before we are ready #
controller.name · string · "controller"
controller.networkPolicy.enabled · bool · false · Enable 'networkPolicy' or not
controller.nodeSelector · object · {"kubernetes.io/os":"linux"} · Node labels for controller pod assignment # Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/ #
controller.podAnnotations · object · {} · Annotations to be added to controller pods #
controller.podLabels · object · {} · Labels to add to the pod container metadata

…(正文过长,页面只展示前面部分,完整内容见仓库)

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Abundancemarble MCP 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Abundancemarble MCP 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Abundancemarble MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Abundancemarble MCP 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Abundancemarble MCP 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、Windsurf、VS Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Abundancemarble MCP 能提供哪些能力?

资料显示能力标签包括 Kubernetes、Claude、云原生。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。