Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Define Temporal Cloud Namespace resource CRD

未关闭
  • 哪里不对？
#5 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 3 天内回复

@tomba7 已经在做这个了。

开始于 2026年10月8日。

评估

这个 Issue 还没有评估数据。

描述

Implement lifecycle management of Temporal Cloud Namespace resources.

Decisions that need to be made about this resource:

  1. Should we "flatten" the CreateNamespaceRequest payload fields into the cloud.temporal.io/v1alpha1.NamespaceSpec struct? In other words, should the CreateNamespaceRequest.spec field's component fields be pulled into NamespaceSpec as top-level fields or should we create a NamespaceSpec.Spec field that mirrors the REST API struct? @jaypipes recommendation here is to flatten.
  2. Should we clean up inconsistent upstream REST API field naming? Example: CreateNamespaceRequest.spec.capacitySpec should be named CreateNamespaceRequest.spec.capacity to be consistent with the other "XXXSpec"-type fields like CreateNamespaceRequest.spec.apiKeyAuth and CreateNamespaceRequest.spec.codecServer. Likewise, there is inconsistency in the naming of certain initialisms (e.g. ID vs. Id) and inconsistency in suffixing fields that refer to another entity with or without Id (e.g. Region vs. RegionId). @jaypipes recommendation here is to clean up the inconsistencies and make the resource operator's custom resource definitions consistent.

Helpful links:

Updated description (2026-10-06):

Goal

A user can describe a Temporal Cloud namespace in a Kubernetes manifest, and invalid manifests are rejected before they reach the operator.

Tasks

  • Decide spec shape and naming (decisions 1 and 2 above)
  • Implement, install and test the CRD
  • Add an example CR object

Definition of done

  • The Go types and the CRD are defined, and the CRD installs on the test cluster.
  • Invalid CRs are rejected at kubectl apply, with tests to prove it.
  • An example CR applies cleanly and is documented in the README.
主要语言
Go
星标
1
派生
0
平均合并
2 天 4 小时
30 天内合并 PR
7

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

temporalio/cloud-operator 的其他 Issue

查看 temporalio/cloud-operator 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。