bug: kubernetes events sent from coder-logstream-kube to coder should not be displayed with a green border

[rowansmithau]

When looking at the image displayed in README.md and when tested locally the events displayed in Coder workspace startup which are received from coder-logstream-kube are logged at Info level which seems to be the reason as to why Coder displays these events with a green border.

We have received a ticket from a customer who is not enthused about this as it confuses end users due to the cycling of the colours and green being used later in the process to indicate the workspace is ready for use. Due to the confusing nature users attempt to connect to workspace apps (web terminal, VS Code Desktop) before they are ready.

At present the workflow is:

Startup process begins: blue
PVC/PV attach, image pull (coder-logstream-kube events): green
Image pulled, startup process continues: blue
All startup steps completed and workspace ready to use: green

Potentially changing the info lines to debug may help here.

Examples:

coder-logstream-kube/logger.go

Lines 217 to 218 in 2e92dd4

	Output: fmt.Sprintf("🐳 %s: %s", newColor(color.Bold).Sprint("Created pod"), pod.Name),
	Level: codersdk.LogLevelInfo,

coder-logstream-kube/logger.go

Lines 286 to 287 in 2e92dd4

	Output: fmt.Sprintf("🐳 %s: %s", newColor(color.Bold).Sprint("Queued pod from ReplicaSet"), replicaSet.Name),
	Level: codersdk.LogLevelInfo,

coder-logstream-kube/logger.go

Line 351 in 2e92dd4

Level: codersdk.LogLevelInfo,