-
Notifications
You must be signed in to change notification settings - Fork 92
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
Added topic on multiple appliance deployment topologies #2020
Conversation
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.
LGTM
@reasonerjt would there be any special requirements if you decided to deploy one VIC appliance and then several standalone Harbor instances that you add to projects as additional registries? I'm thinking about user access. Presumably, the standalone Harbor instances would need to be configured to use the same AD setup as the PSC that the appliance is connected to, correct? |
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.
LGTM
If a Platform Services Controller manages multiple vCenter Server instances, you can deploy multiple appliances to different vCenter Server instances that share that Platform Services Controller. This setup provides the following advantages: | ||
|
||
- All of the user accounts that are configured in the Platform Services Controller are available to all of the vSphere Integrated Containers appliances. | ||
- You can assign diffferent roles to the same user account in different instances of the appliance. For example, a user can be a vSphere Integrated Containers Management Portal administrator for one appliance, but not for another. |
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.
diffferent is a typo
In a large vSphere environment, in which not all vCenter Server instances are located in the same place, or are not all in the same vCenter Single Sign On domain, you can create a hub and spoke configuration: | ||
|
||
- You deploy one vSphere Integrated Containers appliance to a vCenter Server instance in a centralized location. This appliance acts as a hub. | ||
- You deploy one vSphere Integrated Containers appliance to each of the remote vCenter Server instances. |
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.
there one extra space between the
and remote
Thanks @reasonerjt ! Your comments are addressed in 4d99316. |
Fixes #740, fixes #1356.
@zjs and @renmaosheng can you please review?