-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Run the TSB in a separate pod #15672
Run the TSB in a separate pod #15672
Conversation
Build your images and do:
@sdodson What does it take to do the equivalent in the installer? |
Whomever owns TSB should work with @ewolinetz to contribute TSB installation automation to openshift-ansible. Is this optional? Is this installed by default when Service Catalog is enabled? Fully supported in 3.7? need to answer those sort of questions too. |
1b1fe15
to
4ae0bef
Compare
4ae0bef
to
edda314
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, jim-minter The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
This won't make non-conflicting conflicts |
/test extended_conformance_gce |
/retest |
/test extended_networking_minimal |
} else { | ||
// we're running in cluster | ||
// in this case we actually want to construct our own template informer | ||
// eventually the config value drops out as it isn't supported server side |
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.
"config value" refers to c.TemplateNamespaces ?
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.
"config value" refers to c.TemplateNamespaces ?
tempateinformers
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.
so where does the template informer get its config from at that point? and is that something one of your other pulls changes?
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.
so where does the template informer get its config from at that point? and is that something one of your other pulls changes?
5 lines down in this pull.
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.
i'm lost.
In the case where this code is running in a pod (not in the master), you're currently standing up an informer using a client that's created using the in cluster config.
the comment says "eventually the config value drops out". What is meant by eventually, are you referring to a future evolution of this code(my original interpretation), or are you referring to some downstream codepath that dumps the value? And if the latter, what is meant by "drops out"?
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.
the comment says "eventually the config value drops out". What is meant by eventually, are you referring to a future evolution of this code(my original interpretation),
Future evolution removes this code. See e27e5d5#diff-e73d057d1e253024c42b0fec37e12420L59
if err != nil { | ||
return nil, err | ||
} | ||
extrouteclientset, err := extrouteclientset.NewForConfig(saKubeClientConfig) |
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.
externalRouteClient (align w/ other names+case)
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.
externalRouteClient (align w/ other names+case)
pre-existing. happy to do it in a follow on.
/retest |
Router again. I don't see the relationship. I'll try once more /retest |
/retest |
/test extended_conformance_install_update |
SecureServing *genericoptions.SecureServingOptions | ||
Authentication *genericoptions.DelegatingAuthenticationOptions | ||
Authorization *genericoptions.DelegatingAuthorizationOptions | ||
Audit *genericoptions.AuditOptions |
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.
I'm guessing this is making our audit harder, of course. Although the advanced audit is designed to work with multiple api server I'm not 100% sure if that was tested ;) Btw. do we care about upstream audit options here. We haven't decided yet which parts of the advanced audit we will enable and this is literally taking what upstream has.
Automatic merge from submit-queue |
This completes the work necessary to run the TSB in a pod. We should continue to remove the cruft from the old path, but I've included a template which creates a running TSB server in the
openshift-template-service-broker
namespace.@bparees @jim-minter