jetbrains/teamcity-operator本项目处于私有测试阶段。如对本产品感兴趣,请联系TeamCity 支持团队。
kubectl apply -f [***]Operator通过Helm Charts安装。目前helm chart需根据请求提供。
shellhelm upgrade --install teamcity-operator -n teamcity-operator --create-namespace ./teamcity-operator-x.x.x.tgz
用户可通过多种方式使用该operator,以下是详细的使用示例列表。
yamlapiVersion: jetbrains.com/v1beta1 kind: TeamCity metadata: name: teamcity namespace: default finalizers: - "teamcity.jetbrains.com/finalizer" spec: image: jetbrains/teamcity-server mainNode: name: main-node spec: requests: cpu: "400m" memory: "2500Mi" dataDirVolumeClaim: name: teamcity-data-dir volumeMount: name: teamcity-data-dir mountPath: /storage spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi
yamlapiVersion: v1 data: connectionProperties.password: DB_PASSWORD connectionProperties.user: DB_USER connectionUrl: DB_CONNECTION_STRING # 格式 jdbc:mysql://DB_HOST:DB_PORT/SCHEMA_NAME kind: Secret metadata: name: database-properties --- apiVersion: jetbrains.com/v1beta1 kind: TeamCity metadata: name: teamcity-with-database namespace: default finalizers: - "teamcity.jetbrains.com/finalizer" spec: image: jetbrains/teamcity-server databaseSecret: secret: database-properties mainNode: name: main-node spec: env: AWS_DEFAULT_REGION: "eu-west-1" requests: cpu: "400m" memory: "1000Mi" dataDirVolumeClaim: name: teamcity-data-dir volumeMount: name: teamcity-data-dir mountPath: /storage spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi
yamlapiVersion: jetbrains.com/v1beta1 kind: TeamCity metadata: name: teamcity-with-startup-properties namespace: default finalizers: - "teamcity.jetbrains.com/finalizer" spec: image: jetbrains/teamcity-server startupPropertiesConfig: teamcity.startup.maintenance: "false" teamcity.firstStart.setupAdmin.enabled: "false" mainNode: name: main-node spec: requests: cpu: "400m" memory: "1000Mi" dataDirVolumeClaim: name: teamcity-data-dir volumeMount: name: teamcity-data-dir mountPath: /storage spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi
yamlapiVersion: jetbrains.com/v1beta1 kind: TeamCity metadata: name: teamcity-sample-with-ingress namespace: default finalizers: - "teamcity.jetbrains.com/finalizer" spec: image: jetbrains/teamcity-server mainNode: name: main-node spec: requests: cpu: "400m" memory: "1000Mi" dataDirVolumeClaim: name: teamcity-data-dir volumeMount: name: teamcity-data-dir mountPath: /storage spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi serviceList: - name: main-node spec: selector: app.kubernetes.io/name: teamcity-sample-with-ingress app.kubernetes.io/component: teamcity-server app.kubernetes.io/part-of: teamcity ports: - protocol: TCP port: 8111 targetPort: 8111 clusterIP: None ingressList: - name: teamcity-sample-with-ingress annotations: nginx.ingress.kubernetes.io/proxy-read-timeout: "3600" nginx.ingress.kubernetes.io/proxy-send-timeout: "3600" nginx.ingress.kubernetes.io/server-snippets: | location / { proxy_http_version 1.1; proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header Host $host; proxy_set_header Upgrade $http_upgrade; # WebSocket支持 proxy_set_header Connection "upgrade"; # WebSocket支持 } spec: ingressClassName: nginx rules: - host: teamcity.mycompany.com http: paths: - backend: service: name: main-node port: number: 8111 pathType: ImplementationSpecific
yamlapiVersion: jetbrains.com/v1beta1 kind: TeamCity metadata: name: teamcity-with-service-account namespace: default finalizers: - "teamcity.jetbrains.com/finalizer" spec: image: jetbrains/teamcity-server serviceAccount: name: teamcity-service-account annotations: eks.amazonaws.com/role-arn: AWS_ROLE mainNode: name: node spec: requests: cpu: "400m" memory: "1000Mi" dataDirVolumeClaim: name: teamcity-data-dir volumeMount: name: teamcity-data-dir mountPath: /storage spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi
yamlapiVersion: jetbrains.com/v1beta1 kind: TeamCity metadata: name: teamcity-init-containers namespace: default finalizers: - "teamcity.jetbrains.com/finalizer" spec: image: jetbrains/teamcity-server mainNode: name: main-node spec: initContainers: - name: init-myservice image: busybox:1.28 command: [ 'sh', '-c', "echo Hello" ] requests: cpu: "400m" memory: "1000Mi" dataDirVolumeClaim: name: teamcity-data-dir volumeMount: name: teamcity-data-dir mountPath: /storage spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi
yamlapiVersion: jetbrains.com/v1beta1 kind: TeamCity metadata: name: teamcity-sample-with-secondary-node-read-only namespace: default finalizers: - "teamcity.jetbrains.com/finalizer" spec: image: jetbrains/teamcity-server dataDirVolumeClaim: name: teamcity-data-dir volumeMount: name: teamcity-data-dir mountPath: /storage spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi mainNode: name: main-node spec: requests: cpu: "1000m" memory: "2500Mi" secondaryNodes: - name: secondary-node spec: requests: cpu: "1000m" memory: "2500Mi"
yamlapiVersion: jetbrains.com/v1beta1 kind: TeamCity metadata: name: teamcity-sample-with-secondary-node namespace: default finalizers: - "teamcity.jetbrains.com/finalizer" spec: image: jetbrains/teamcity-server startupPropertiesConfig: teamcity.startup.maintenance: "false" teamcity.firstStart.setupAdmin.enabled: "false" dataDirVolumeClaim: name: teamcity-data-dir volumeMount: name: teamcity-data-dir mountPath: /storage spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi mainNode: name: main-node annotations: cluster-autoscaler.kubernetes.io/safe-to-evict: "true" spec: requests: cpu: "1000m" memory: "2500Mi" responsibilities: [ "MAIN_NODE", "CAN_PROCESS_BUILD_MESSAGES", "CAN_CHECK_FOR_CHANGES", "CAN_PROCESS_BUILD_TRIGGERS", "CAN_PROCESS_USER_DATA_MODIFICATION_REQUESTS"] secondaryNodes: - name: secondary-node-0 annotations: cluster-autoscaler.kubernetes.io/safe-to-evict: "false" spec: requests: cpu: "1000m" memory: "2500Mi" responsibilities: ["CAN_PROCESS_BUILD_MESSAGES", "CAN_CHECK_FOR_CHANGES", "CAN_PROCESS_BUILD_TRIGGERS", "CAN_PROCESS_USER_DATA_MODIFICATION_REQUESTS"] - name: secondary-node-1 annotations: cluster-autoscaler.kubernetes.io/safe-to-evict: "false" spec: requests: cpu: "1000m" memory: "2500Mi" responsibilities: [ "CAN_PROCESS_BUILD_MESSAGES", "CAN_CHECK_FOR_CHANGES", "CAN_PROCESS_BUILD_TRIGGERS", "CAN_PROCESS_USER_DATA_MODIFICATION_REQUESTS" ]

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
无需登录使用专属域名
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
Harbor Proxy Repository 对接专属域名
Portainer Registries 加速拉取
Nexus3 Docker Proxy 内网缓存
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
manifest unknown 错误
TLS 证书验证失败
DNS 解析超时
410 错误:版本过低
402 错误:流量耗尽
身份认证失败错误
429 限流错误
凭证保存错误
来自真实用户的反馈,见证轩辕镜像的优质服务