kubernetes / kops

Kubernetes Operations (kOps) - Production Grade k8s Installation, Upgrades and Management
https://kops.sigs.k8s.io/
Apache License 2.0
15.96k stars 4.65k forks source link

[Helped]so many TODO in kops/pkg/ , can we solve some of them? #8238

Closed tanjunchen closed 4 years ago

tanjunchen commented 4 years ago

There are so many TODO in kops , I guess that we can solve or improve some of them. I open an issue to record them. Here are TODO under /pkg folder.

If the following TODO does not exist, I hope you can reply this TODO in here, so I can update this list in time. Or you have solved one of the TODOs and hope you can associate this issue for easy tracking.

grep -rs --exclude-dir="vendor/"   "TODO"  | wc -l
767
bittopaz commented 4 years ago

Great initiative!

rifelpet commented 4 years ago

Agreed! Just to make the list a bit shorter, I notice we can ignore any of the matches under docs/apireference/build and any of the Binary file ____ matches too. Some of the markdown files matched but dont have the actual todo text in your list (like docs/tutorial/working-with-instancegroups.md), possibly because they're in markdown comments <!-- --!> which the GH issue will treat as a comment itself?

Beyond that I think we could triage many of these based on the most commonly used packages and create individual GH issues for them, perhaps labeling them with good-starter-issue,

tanjunchen commented 4 years ago

/help /good-starter-issue

k8s-ci-robot commented 4 years ago

@tanjunchen: This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to [this](https://github.com/kubernetes/kops/issues/8238): >/help >/good-starter-issue Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
tanjunchen commented 4 years ago

Because this issue is a bit big, I will consider listing TODO as a package and excluding some unnecessary files.If possible, I will separate them into several issues .Thank you for your suggestions. @rifelpet

rifelpet commented 4 years ago

Agreed, we can add good-starter-issue to smaller issues that we separate from this big issue.

tanjunchen commented 4 years ago

@rifelpet I have ignore some files . next , how to separate them?welcome to suggestions.

johngmyers commented 4 years ago

Since I'm trying to make substantial changes to pkg/instancegroups, I'd appreciate if people could hold off soliciting low-value conflicting PRs there for now.

ryan-dyer-sp commented 4 years ago

RE: tokenauthfile removal . Removing of this flag is required by CIS benchmarks. I see kops is still setting this flag and the value (known_tokens.csv) does contain entries. So is this safe to actually remove? I'm happy to submit a PR to rip it out, but I don't know anything about this from an actual code and usage perspective.

Nilubkal commented 4 years ago

@ryan-dyer-sp i was dealing with the exact same issue ( reported by CIS benchmarks). It seems that its hard-coded here nodeup/pkg/model/kube_apiserver.go

288 // buildPod is responsible for generating the kube-apiserver pod and thus manifest file
289 func (b *KubeAPIServerBuilder) buildPod() (*v1.Pod, error) {
290   kubeAPIServer := b.Cluster.Spec.KubeAPIServer
291   kubeAPIServer.ClientCAFile = filepath.Join(b.PathSrvKubernetes(), "ca.crt")
292   kubeAPIServer.TLSCertFile = filepath.Join(b.PathSrvKubernetes(), "server.cert")
293   kubeAPIServer.TLSPrivateKeyFile = filepath.Join(b.PathSrvKubernetes(), "server.key")
294   kubeAPIServer.TokenAuthFile = filepath.Join(b.PathSrvKubernetes(), "known_tokens.csv")

Is it foreseen a removal of the flag in future releases ? I was not able to disable it by modifying tokenAuthFile under the kubeAPIServer when i deploy the cluster via a template.

fejta-bot commented 4 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale