Project settings allow a Project Manager to review and modify the configuration associated with an existing Project.
Project configuration includes:
Changes to Project settings can affect future Space creation and, in some cases, existing Spaces. Review changes carefully before saving them.
To manage an existing Project:
https://cloud.k2view.com
Review the Project information and update it when necessary.
Use Project names and descriptions that clearly identify the implementation and remain meaningful across its development, QA, staging, and production Spaces.
A Project normally represents the implementation rather than a particular runtime environment.
The Project's Git configuration associates it with the repository containing the K2view project source.
If the repository or Git token changes, update the Project configuration accordingly.
Before saving a Git configuration change, verify that:
For detailed information, see Configure Git.
A Project can have one or more Space Profiles available for creating Spaces.
For each Space Profile, review the associated Fabric Image and other available profile configuration.
The Space Profile defines the runtime topology and resources, while the Fabric Image determines the Fabric version.
Changing the Fabric Image associated with a Space Profile can make an upgrade available to existing eligible Spaces using that profile. It does not immediately upgrade those Spaces.
For information about Fabric versions and upgrades, see Fabric Versions and Upgrades.
After modifying the Project:
Changes become part of the Project configuration used by subsequent K2cloud operations.
A Site is not selected as a Project setting.
The Site is selected when a Space is created and determines where that particular Space is deployed.
This allows Spaces belonging to the same Project to be deployed to different Sites when required.
For more information, see Sites.
Project settings allow a Project Manager to review and modify the configuration associated with an existing Project.
Project configuration includes:
Changes to Project settings can affect future Space creation and, in some cases, existing Spaces. Review changes carefully before saving them.
To manage an existing Project:
https://cloud.k2view.com
Review the Project information and update it when necessary.
Use Project names and descriptions that clearly identify the implementation and remain meaningful across its development, QA, staging, and production Spaces.
A Project normally represents the implementation rather than a particular runtime environment.
The Project's Git configuration associates it with the repository containing the K2view project source.
If the repository or Git token changes, update the Project configuration accordingly.
Before saving a Git configuration change, verify that:
For detailed information, see Configure Git.
A Project can have one or more Space Profiles available for creating Spaces.
For each Space Profile, review the associated Fabric Image and other available profile configuration.
The Space Profile defines the runtime topology and resources, while the Fabric Image determines the Fabric version.
Changing the Fabric Image associated with a Space Profile can make an upgrade available to existing eligible Spaces using that profile. It does not immediately upgrade those Spaces.
For information about Fabric versions and upgrades, see Fabric Versions and Upgrades.
After modifying the Project:
Changes become part of the Project configuration used by subsequent K2cloud operations.
A Site is not selected as a Project setting.
The Site is selected when a Space is created and determines where that particular Space is deployed.
This allows Spaces belonging to the same Project to be deployed to different Sites when required.
For more information, see Sites.