Rancher
Create an integration to manage access to a Rancher instance
Last updated
Was this helpful?
Create an integration to manage access to a Rancher instance
Last updated
Was this helpful?
Rancher is a Kubernetes management platform that simplifies the deployment and management of clusters across any environment, enhancing flexibility, scalability, and resource efficiency.
Through this integration, Apono helps you discover your Kubernetes resources and securely manage access through your Rancher instance.
Rancher Admin Access
User account with admin permissions to create a new user account
Follow these steps to create a dedicated user for Apono:
In Rancher, with a user-friendly name, such as apono-provisionser-user-role.
Locate the new role.
Click ☰ > Edit YAML.
Above the metadata
property, add the cluster-owner
role.
Assigning the cluster-owner
role via inheritedClusterRoles
does not provide access to the local
cluster (the Rancher control plane cluster). This role inheritance applies only to downstream user clusters and excludes Rancher’s internal management plane.
Click Save.
Assign the new dedicated user (apono-provisioner-user) to the new local user.
You can also use the steps below to integrate with Apono using Terraform. In step 10, instead of clicking Confirm, follow the Are you integrating with Apono using Terraform? guidance.
Follow these steps to complete the integration:
Under Discovery, click Next. The Apono connector section expands.
From the dropdown menu, select a connector.
Click Next. The Integration Config section expands.
Define the Integration Config settings.
Integration Name
Unique, alphanumeric, user-friendly name used to identify the integration when constructing an access flow
Host
Hostname of the Rancher server
Port
Rancher port value
Certificate Authority (optional)
(Optional) Ensures that the Kubernetes API server you are communicating with is trusted and authentic
Leave this field blank to connect the cluster where the Apono connector is deployed.
Rancher UI URL (optional)
(Optional) URL of your Rancher UI
This URL must be reachable from all the hosts that you add.
Click Next. The Secret Store section expands.
Click Next. The Get more with Apono section expands.
Define the Get more with Apono settings.
Credential Rotation
(Optional) Number of days after which the database credentials must be rotated
User cleanup after access is revoked (in days)
(Optional) Defines the number of days after access has been revoked that the user should be deleted
Custom Access Details
(Optional) Instructions explaining how to access this integration's resources Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to 400 characters. To view the message as it appears to end users, click Preview.
Integration Owner
From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
From the Value dropdown menu, select one or multiple users or groups.
NOTE: When Resource Owner is defined, an Integration Owner must be defined.
Resource Owner
Enter a Key name. This value is the name of the tag created in your cloud environment.
From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated. Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.
NOTE: When this setting is defined, an Integration Owner must also be defined.
Click Confirm.
with a user-friendly name, such as apono-provisioner-user.
Logged in as the new dedicated user (apono-provisioner-user), and copy the Access Key and Secret Key.
Create a for the dedicated user to use during the Apono integration setup. Use the values from step 7 to generate the secret.
You can now .
On the tab, click Rancher. The Connect Integration page appears.
If the desired connector is not listed, click + Add new connector and follow the instructions for creating a connector (, , , ).
.
Learn more about the .
Learn more about .
(Optional) Fallback approver if no is found Follow these steps to define one or several integration owners:
(Optional) Group or role responsible for managing access approvals or rejections for the resource Follow these steps to define one or several :
Refer to for more details about the schema definition.
Now that you have completed this integration, you can that grant permission to your Rancher instance.