Add status conditions to Shim status

[tillknuesting]

Describe your changes

Implement status conditions in Shim status to reflect readiness based on node provisioning status. #51

Issue ticket number and link

runtime-class-manager/internal/controller/shim_controller.go

Line 192 in c65f356

// TODO: include proper status conditions to update

Checklist before requesting a review

• I have performed a self-review of my code
• If it is a core feature, I have added thorough tests.
• I tested the changes with the following distributions:
  • Kind
  • MiniKube
  • MicroK8s
  • Rancher RKE2
  • Azure AKS
  • GCP GKE (Ubuntu nodes)
  • AWS EKS (AmazonLinux2 nodes)
  • AWS EKS (Ubuntu nodes)
  • Digital Ocean Kubernetes

[tillknuesting]

@voigt @0xE282B0, Could you give feedback on whether this PR meets the intention expressed in the TODO?

[0xE282B0]

Hey @tillknuesting,
Awesome that you are contributing!
We're currently on a conference marathon, but we'll have a look later 😁

[voigt]

Hey @tillknuesting,
Thank you for the PR and tackling the issue.

Apart from the implementation, a significant part of the issue is investigating the different possible states and under which conditions they occur. IMO, there are at least three states:

• ready (...)
• pending (jobs are scheduled/running; not all finished)
• failed (at least one job wasn't successful / got stuck?)

Other states may be reasonable as well.