Comments (7)
demobox
commented on August 14, 2024
Do you mean multiple GCP projects or multiple Spinnaker instances? The intended design is that the same spinnaker-for-gcp repo can be used to manage many Spinnaker instances - the pull_config.sh command will ensure the configuration of the targeted Spinnaker instance is retrieved and used.
from spinnaker-for-gcp.
wilddog64
commented on August 14, 2024
Multiple projects.
…On Fri, Nov 1, 2019 at 13:31 Andrew Phillips ***@***.***> wrote:
Do you mean multiple GCP projects or multiple Spinnaker instances? The
intended design is that the *same* spinnaker-for-gcp repo can be used to
manage *many* Spinnaker instances
<https://cloud.google.com/docs/ci-cd/spinnaker/spinnaker-for-gcp#manage_multiple_spinnaker_installations>
- the pull_config.sh command will ensure the configuration of the
targeted Spinnaker instance is retrieved and used.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#144?email_source=notifications&email_token=AAFWGVHQN5XYJJOHPSLLYI3QRSGZ5A5CNFSM4JHTMPE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC4CT3Q#issuecomment-548940270>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFWGVFULNENYCOXEA5TAKTQRSGZ5ANCNFSM4JHTMPEQ>
.
from spinnaker-for-gcp.
duftler
commented on August 14, 2024
The scripts should only be run from the $HOME/spinnaker-for-gcp directory, as designed.
If the instructions are followed, it can safely be used to manage multiple Spinnaker installations, across multiple GCP projects.
There are some details here on managing multiple installations. If you follow those steps, all that remains is to refresh the management console via ~/spinnaker-for-gcp/scripts/manage/update_console.sh.
We still recommend an admin/operator wishing to manage an installation start from the Kubernetes Engine->Applications view in the Cloud Console. The link in the application details view will open Cloud Shell and bring up the management console. Then you need to ensure you are corrected to the correct cluster, pull the config, and refresh the console. These are the exact commands that come up in the console by default when cloning the repo.
The workflow is basically:
- Open Cloud Shell and the management console (that is, the documentation in the right-hand pane)
- Ensure you are corrected to the correct cluster in the correct project
- Pull the config from that Spinnaker installation
- Refresh the management console so the various commands and links properly reflect the installation being managed
from spinnaker-for-gcp.
wilddog64
commented on August 14, 2024
What about multiple projects? I believe scripts can handle multiple
spinnaker instances. But I wonder if it can handle different project.
…On Mon, Nov 4, 2019 at 6:07 AM Matt Duftler ***@***.***> wrote:
The scripts should only be run from the $HOME/spinnaker-for-gcp
directory, as designed.
If the instructions are followed, it can safely be used to manage multiple
Spinnaker installations, across multiple GCP projects.
There are some details here
<https://cloud.google.com/docs/ci-cd/spinnaker/spinnaker-for-gcp#manage_multiple_spinnaker_installations>
on managing multiple installations. If you follow those steps, all that
remains is to refresh the management console via
~/spinnaker-for-gcp/scripts/manage/update_console.sh.
We still recommend an admin/operator wishing to manage an installation
start from the Kubernetes Engine->Applications view in the Cloud Console.
The link in the application details view will open Cloud Shell and bring up
the management console. Then you need to ensure you are corrected to the
correct cluster, pull the config, and refresh the console. These are the
exact commands that come up in the console by default when cloning the repo.
The workflow is basically:
- Open Cloud Shell and the management console (that is, the
documentation in the right-hand pane)
- Ensure you are corrected to the correct cluster in the correct
project
- Pull the config from that Spinnaker installation
- Refresh the management console so the various commands and links
properly reflect the installation being managed
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#144?email_source=notifications&email_token=AAFWGVHBUSBXQVKONHYRFF3QSAUBJA5CNFSM4JHTMPE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC7LMBA#issuecomment-549369348>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFWGVAQ7OAZA24PCWSHRFLQSAUBJANCNFSM4JHTMPEQ>
.
from spinnaker-for-gcp.
duftler
commented on August 14, 2024
Yes, it works across multiple projects. This is why the first section of the management console guidance requires you to select a project.
from spinnaker-for-gcp.
wilddog64
commented on August 14, 2024
As far as I know spinnaker-for-gcp does not work well with multiple
projects. If you switch to a different project, besides you have to switch
project, you also need to clean up properties file. I think ideally, the
scripts should be able to resolve execution path. This way, I can use a
different directory to manage different project.
…On Tue, Nov 5, 2019 at 4:46 AM Matt Duftler ***@***.***> wrote:
Yes, it works across multiple projects. This is why the first section of
the management console guidance requires you to select a project.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#144?email_source=notifications&email_token=AAFWGVHMHUL7EWMDQRBZXNDQSFTL3A5CNFSM4JHTMPE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDCWSAQ#issuecomment-549808386>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFWGVCU6DB6JD45ARZKZULQSFTL3ANCNFSM4JHTMPEQ>
.
from spinnaker-for-gcp.
duftler
commented on August 14, 2024
If you switch to a different project, besides you have to switch
project, you also need to clean up properties file.
This is incorrect.
The pull_config.sh script replaces all of the relevant config files, including the properties file (you can see the actual command here: https://github.com/GoogleCloudPlatform/spinnaker-for-gcp/blob/master/scripts/manage/pull_config.sh#L55).
If you are switching projects and your properties file is not being updated, please open an issue with exact steps to reproduce.
from spinnaker-for-gcp.
Related Issues (20)
- No valid versions with the prefix "1.18.17" found. HOT 1
- Spinnaker 1.26.6 still uses legacy UI? Don't see gcs artifact account when creating stage. HOT 1
- Spinnaker is messed up after resize cluster to 0 nodes HOT 2
- Doesn't work, GKE version outdated? HOT 1
- request: mention "Control plane authorised networks" in documentation
- Issue in Connect to Spinnaker - on Step 2
- Application information missing in Spinnaker after re-adding GKE accounts HOT 2
- Random identifier generation can hang
- `--enable-stackdriver-kubernetes` being deprecated when creating GKE cluster.
- When fiat is enabled service and deployment labels are not applied
- `setup.sh` enables Cloud APIs that are not required by all deployments HOT 1
- Automatically select kube context.
- `scripts/manage/connect_to_redis.sh` is flakey
- ! ERROR Failed to backup user file
- Unable to use the repository to deploy Spinnaker on GCP HOT 1
- Is the spinnaker-for-gcp repository still active?
- Is the spinnaker-for-gcp repository still active?
- Unable to configure Email configuration
- Modify function setup to automatically select available nodejs runtimes
- getting error while adding the gke account by running the script HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spinnaker-for-gcp.