-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Provider controller #408
Draft
alexgeorgousis
wants to merge
14
commits into
master
Choose a base branch
from
provider-controller
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexgeorgousis
force-pushed
the
provider-controller
branch
6 times, most recently
from
December 9, 2024 11:30
ee146de
to
7ca4231
Compare
alexgeorgousis
commented
Dec 9, 2024
type ProviderStatus struct { | ||
Conditions Conditions `json:"conditions,omitempty"` | ||
Spec ProviderSpec `json:"spec,omitempty"` | ||
Status Status `json:"status,omitempty"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We previously used a dedicated ProviderStatus
struct for the provider CRD status, but we didn't see the point in it because:
- It only has a single field,
Conditions
, which is part of the defaultStatus
struct already - We don't set the provider status anywhere (except for tests, just so they compile)
So we removed ProviderStatus
and just used the default Status
struct.
alexgeorgousis
force-pushed
the
provider-controller
branch
9 times, most recently
from
December 12, 2024 10:27
94500b9
to
c555c38
Compare
TobyPinfold
force-pushed
the
provider-controller
branch
from
December 12, 2024 11:59
0667f07
to
a1747ca
Compare
grahamia
force-pushed
the
provider-controller
branch
from
December 16, 2024 10:49
1b5556a
to
e477814
Compare
aidandunlop
force-pushed
the
provider-controller
branch
from
December 19, 2024 14:52
4cf3376
to
438053b
Compare
alexgeorgousis
force-pushed
the
provider-controller
branch
9 times, most recently
from
December 27, 2024 10:26
90605f7
to
c98ef2d
Compare
alexgeorgousis
force-pushed
the
provider-controller
branch
2 times, most recently
from
December 30, 2024 14:57
4e11412
to
014c743
Compare
alexgeorgousis
force-pushed
the
provider-controller
branch
from
January 10, 2025 10:34
5fb45f4
to
aa9ce00
Compare
grahamia
force-pushed
the
provider-controller
branch
from
January 10, 2025 11:08
aa9ce00
to
ddef6a9
Compare
alexgeorgousis
force-pushed
the
provider-controller
branch
6 times, most recently
from
January 16, 2025 15:53
b293936
to
6d1002c
Compare
… mounted configmap volume to override provider behaviour
…oviders own deployments
This was causing errors while loading config to not be logged!
alexgeorgousis
force-pushed
the
provider-controller
branch
7 times, most recently
from
January 17, 2025 09:51
b257e07
to
9feb559
Compare
alexgeorgousis
force-pushed
the
provider-controller
branch
from
January 17, 2025 16:11
9feb559
to
f58ede9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #332
Tasks
Deployment
from the controllerDeployThis will be managed using Env vars within the deployment, to avoid the need to manage another configmap resource.ConfigMap
(introduced in Step 4) needed byDeployment
, Should the controller deploy this or should we let users optionally deploy it separately as a way to configure a provider?Use state transition logic like in other controllers (though we don't this in the runconfiguration controller, we just have aWould require a rework of the state transition logic to not be tied to workflows, this should be done separately as it will be a large piece of workTODO
to do it)Provider
resourcesSynchronizationState
onProvider
resourceSynchronized
condition (we do this for all other resources)???ObservedGeneration
? (It's on the CRD but we never set it explicitly)type
isn't used anywhere and, if not, remove it from the CRD (and wherever else it's currently referenced)manager-providers-viewer-rolebinding.yaml
toroles.yaml
Provider
CRD, do we need av1alpha7
release?v1alpha6
yet, so we can add it to itUseful Links