You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi team, I would like to know if it's possible to use OKit without the config file and without authenticating with IDSC.
In our scenario it is undesirable to create API tokens for every user that needs to connect to OKit, therefore we wanted to avoid using the ~/.oci/config file. We tried to install OKit on a VM created within OCI and follow the steps described in the Native chapter in your documentation, then we created a Dynamic Group consisting of the VM we just installed OKit in, then we attached a policy to that Dynamic Group allowing the instance to manage everything in the tenancy. When I managed to use OKit I tried exporting a simple deployment as a stack but it required me to input a configuration profile, something which we don't want.
We also tried following the Install on OCI Instance chapter but we didn't want to use the IDCS service as it comes with a cost.
Why can't I use the instance principal feature to use and deploy stacks on OCI via OKit? We have deployed another script which automatically shuts down the instances based on a calendar and that service uses the instance principal feature, why can't we use OKit in the same way?
Many thanks and best regards.
N
The text was updated successfully, but these errors were encountered:
Hi team, I would like to know if it's possible to use OKit without the config file and without authenticating with IDSC.
In our scenario it is undesirable to create API tokens for every user that needs to connect to OKit, therefore we wanted to avoid using the
~/.oci/config
file. We tried to install OKit on a VM created within OCI and follow the steps described in the Native chapter in your documentation, then we created a Dynamic Group consisting of the VM we just installed OKit in, then we attached a policy to that Dynamic Group allowing the instance to manage everything in the tenancy. When I managed to use OKit I tried exporting a simple deployment as a stack but it required me to input a configuration profile, something which we don't want.We also tried following the Install on OCI Instance chapter but we didn't want to use the IDCS service as it comes with a cost.
Why can't I use the instance principal feature to use and deploy stacks on OCI via OKit? We have deployed another script which automatically shuts down the instances based on a calendar and that service uses the instance principal feature, why can't we use OKit in the same way?
Many thanks and best regards.
N
The text was updated successfully, but these errors were encountered: