Skip to content
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.

Papercuts in kubernetes server install #2412

Merged
merged 5 commits into from
Oct 6, 2021
Merged

Papercuts in kubernetes server install #2412

merged 5 commits into from
Oct 6, 2021

Conversation

izaaklauer
Copy link
Contributor

  • Fixes a problem where deployments would be marked as "Degraded", but were actually fine
  • Adds a new clusterrole and clusterrolebinding to the install flow to allow the runner to get and list nodes, which it needs to discover the IP of nodeport type services.
  • If for some reason the nodeport ip discovery fails, don't fail the whole release (per @evanphx 's suggestion)

@izaaklauer izaaklauer requested a review from a team October 4, 2021 19:10
@izaaklauer izaaklauer marked this pull request as ready for review October 4, 2021 19:10
Copy link
Contributor

@krantzinator krantzinator left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice docs updates as well

Copy link
Member

@briancain briancain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some minor requests! 🧻 ✂️ Looks good though, agree on making the deployments status simpler, hopefully the real issues get surfaced in its pods status.

builtin/k8s/releaser.go Outdated Show resolved Hide resolved
internal/serverinstall/k8s.go Outdated Show resolved Hide resolved
Copy link
Contributor

@catsby catsby left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just minor nit/questions that I don't consider blockers

// Print in a standalone step, so the output won't get overwritten if we add more step output later in the future.
errStep := sg.Add("Cannot determine release URL for nodeport service due to failure to list nodes: %s", err)
errStep.Status(terminal.StatusError)
errStep.Done()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: should we use the included log here and log this error as well? I don't see log used much (or at all?) in this method, but if we're not returning the error we may only be showing it in a UI in this case, right? Just a thought, as mentioned I don't see log used much in this method anyway

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are a bunch of places where I think ui messages would be super helpful in logs - honestly, i've been meaning to solve this eventually with #2075, so i've been reticent to duplicate messages between ui and the logs. If you think this is an especially important one though, I can see putting a log here.

internal/serverinstall/k8s.go Show resolved Hide resolved
internal/serverinstall/k8s.go Show resolved Hide resolved
internal/serverinstall/k8s.go Outdated Show resolved Hide resolved
@izaaklauer izaaklauer merged commit d3138dc into main Oct 6, 2021
@izaaklauer izaaklauer deleted the k8s-install-fixup branch October 6, 2021 12:55
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants