Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Feature]: End user can deploy controllers to cluster #23

Closed
Birdrock opened this issue Aug 27, 2021 · 0 comments · Fixed by #38
Closed

[Feature]: End user can deploy controllers to cluster #23

Birdrock opened this issue Aug 27, 2021 · 0 comments · Fixed by #38
Assignees
@Birdrock @akrishna90

Comments

@Birdrock
Copy link
Member

Birdrock commented Aug 27, 2021 •
edited
Loading

Blockers/Dependencies

No response

Background

As an end user
I want to be able to deploy the controllers to a cluster
So that I can see resources reconciled

Acceptance Criteria

GIVEN I clone the repo and see the deployment yaml
WHEN I follow README steps to kubectl apply it
THEN I see a controller pod start up

Dev Notes

  • This should be a static deployment yaml.
  • We should think about how we keep the the static deployment in sync with our development process. Create a new story to automate this.
  • This may require some RBAC work as controllers are expanded.
  • The acceptance criteria specify README steps - these need to be updated.
@Birdrock Birdrock mentioned this issue Aug 27, 2021
Closed
davewalter added a commit that referenced this issue Sep 3, 2021
@acosta11 @davewalter
Remove unused CFRoute.Port
7917e39 
Issue: [#23](cloudfoundry/cf-k8s-api#23)

- initial implementation only supports HTTP routing, which does not
  allow users to specify a port

Co-authored-by: Dave Walter <walterda@vmware.com>
@Birdrock Birdrock mentioned this issue Sep 9, 2021
Merged
@Birdrock Birdrock linked a pull request Sep 13, 2021 that will close this issue
Create reference yaml to apply cf-k8s-controllers #38
Merged
Birdrock added a commit that referenced this issue Sep 13, 2021
@Birdrock
Merge pull request #38 from cloudfoundry/issues-23-kubectl-reference-…
9d99dbd 
…yaml

Create reference yaml to apply cf-k8s-controllers

Resolves #23
gnovv pushed a commit that referenced this issue Sep 13, 2021
@davewalter @acosta11
Remove unused CFRoute.Port (#36)
2a37d31 
Issue: [#23](cloudfoundry/cf-k8s-api#23)

- initial implementation only supports HTTP routing, which does not
  allow users to specify a port

Co-authored-by: Dave Walter <walterda@vmware.com>

Co-authored-by: Andrew Costa <ancosta@vmware.com>
@Birdrock Birdrock mentioned this issue Sep 16, 2021
Merged
Birdrock pushed a commit that referenced this issue Oct 29, 2021
@acosta11 @davewalter
Implement GET /api/v3/routes/:guid (#33)
08be9ca 
Issue #23
- Updated cf-k8s-controllers for CFRoute scheme
- Updated Not Found Error shared helper to take resource type

Co-authored-by: Dave Walter <walterda@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Birdrock Birdrock

@akrishna90 akrishna90

Labels
None yet
Projects
Korifi - Backlog
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Create reference yaml to apply cf-k8s-controllers cloudfoundry/korifi
2 participants
@Birdrock @akrishna90