The Administration section explains all the administrative features of Kore that allow you to define what resources teams can use, which clouds they have access to, and more. If you are not a Kore administrator, see the Developer Guide for information on how to use Kore to deploy your applications.
In order to administer Kore, you must be in the
kore-admin team. By default, the
first user added to Kore is placed in this team, and that user can add administrative privileges to other users.
This topic lists some important activities you'll do as a Kore administrator and points you to where you can find more information about them.
You can log in using either the Kore UI or CLI. To download the CLI, see Get the CLI for instructions.
For login instructions see:
You'll have to give Kore access to one or more of your cloud accounts, and allocate the accounts to one or more teams in Kore. Then development teams will be able to self-serve to create environments for their applications.
For instructions, head to Cloud Accounts.
Kore comes with default cluster plans for each cloud provider we support. The default cluster plans provide a set of preset Kubernetes cluster parameters based on whether the cluster will be used for development or production. With cluster plans, development teams choose the plan they need, and create the cluster quickly without worrying about Kubernetes cluster settings.
Cluster policies define which cluster plan parameters can be modified by team members. This lets you control who can modify cluster plans and which parameters they can change. This is also gives you a way to provide more flexibility to teams to change cluster settings. Kore comes with default cluster plans for each cloud provider.
For more information, see Cluster Plans.
Kore uses default IP ranges defined in cluster plans. However, you can control the IP address ranges used to build team clusters. Go to Networking Overview to find out more, including how to set up AWS VPC network peering.
To make it convenient for developers to have available domains for their applications, you can create shared DNS zones. Then when a team creates a cluster, DNS zones are automatically created for that cluster, based on the shared DNS zones you created. Teams can also add their own custom domains for applications.
For more information and instructions, see DNS.
If SSO with an identity provider (IDP) is not already set up, you can set it up. See User Authentication Providers.
If you're not using SSO, want to add specific local users, or want to manage users via CI pipeline, see User Management.
You can view the security status for all clusters and cluster plans, and the underlying security compliance rules. Head to View Security Status for details.