-
Notifications
You must be signed in to change notification settings - Fork 61
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
Just question for core platform whithout GCP #70
Comments
Hi, right now the GCP dependencies are not well isolated. Good news though is that we're working on introducing more configuration options to allow a non-GCP setup. If you have more details on your setup that you could share, it could help us to design this right. E.g. we need some auth to ensure only legitimate admins can register robot/onprem clusters to the orchestration cluster. Not doing this might only be a fesible is a fully isolated local setup. |
Thnks for your answer. I am doing ros2enabled device on cloudrobotics platform, which can communicate among them on even inter-network. Actually ros2 dds cannot do that though for now. |
@swgu931 I tried to deploy cloud robotics on different environments a while ago in a branch. It is not very tidy, because there are different stages combined in this branch and I did not touch terraform configuration
I might be able to include that into the project when GCP dependencies are better isolated as @ensonic suggested. Until then feel free to have a look at my changes 😄 |
@oliver-goetz thanks for your work and answer, I did have quick review on your branch, I think it should be compiled but I installed on GKE through quickstart guide. Thanks again, |
+1 Any update on this? |
+1 Any update?? |
In order to make progress it would be helpful to understand:
|
My issue is not the real issue.
This is the only question if we can make use of googlecloudrobotics's core platform without GCP.
It means I want to check connectivity and application robot core and my on-prem Kubernetes cluster.
Of coure don't care authentication and charging system, only pay attention to Layer2(app management), Layer3(Managed repo).
The text was updated successfully, but these errors were encountered: