vania-janet/multiturn-rag-retrieval-data huggingface dataset:
This tool can also be used to gather information about your IBM® Cloud Foundry applications, even without migrating the applications. Use the move2kube collect -a cf command to obtain information about your IBM® Cloud Foundry applications, similar to the way described manually in [IBM® Cloud Foundry application deployment analysis.](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecation_deploy_analysis)

The tool sill not work for all users, all apps, and all cases, but it is a starting point to help you in your migration planning. Even if you hand-migrate much of your application later, the tool can be a first pass to see how to migrate. This tool is more useful to move to a service with base Kubernetes capability. A service such as IBM Cloud Code Engine might not benefit as much since IBM Cloud Code Engine does so many things automatically for you, unlike most direct-Kubernetes offerings.

This tool is an Open Source project. No guarantees are made by either the Open Source project, konveyor.io, or IBM.

Investigate and evaluate the tool at [Konveyor.io](http://Konveyor.io) and [Move2Kube](https://move2kube.konveyor.io/). These resources include an overview of the tools and installation steps.

If you want to use a sample Cloud Foundry application to test this migration capability, the following is a sample app with instructions on how to deploy to IBM® Cloud Foundry. You can then use the app to try move2kube steps.



 Sample Cloud Foundry Application 

The sample application is called enterprise-app, and is located [here](https://github.com/konveyor/move2kube-demos/tree/main/samples/enterprise-app/src) There are also a [number of other Tutorials and Examples you can explore.](https://move2kube.konveyor.io/tutorials)

The Enterprise-App consists of several microservices that work together to create a retail application that handles various customer transactions for the business.
To list monitoring configurations that you manually set up without using the IBM Cloud Kubernetes Service observability plug-in, you must first make this configuration available to the plug-in by using the [ibmcloud ob monitoring agent discover](https://cloud.ibm.com/docs/containers?topic=containers-observability_climonitoring_agent_discover) command.

ibmcloud ob monitoring config list --cluster CLUSTER

Minimum required permissions:



* Viewer platform access role and Reader service access role for the ibm-observe Kubernetes namespaces in IBM Cloud Kubernetes Service.
* Viewer platform access role for IBM Cloud Monitoring



Command options:

--cluster CLUSTER
: The name or ID of the cluster for which you want to list existing Monitoring configurations. This value is required.





 ibmcloud ob monitoring config enable public-endpoint|private-endpoint 

Virtual Private Cloud

Classic infrastructure

Use the public or private cloud service endpoint to send metrics from your cluster to your Monitoring service instance.

To use the private cloud service endpoint, your cluster must be enabled for using private cloud service endpoints.

ibmcloud ob monitoring config enable public-endpoint|private-endpoint --cluster CLUSTER --instance MONITORING_INSTANCE

Minimum required permissions:



* Administrator platform access role and Manager service access role for all Kubernetes namespaces in IBM Cloud Kubernetes Service
* Editor platform access role and Manager server access role for IBM Cloud Monitoring



Command options:

public-endpoint|private-endpoint
: Enter public-endpoint to use the public cloud service endpoint of your IBM Cloud Monitoring service instance, or private-endpoint to use the private cloud service endpoint to send metrics from your cluster. This value is required. To use the private cloud service endpoint, your cluster must be enabled for using private cloud service endpoints.

--cluster CLUSTER
: The name or ID of the cluster for which you want to enable the private or public cloud service endpoint to connect to your Monitoring service instance. To retrieve your cluster name or ID, run ibmcloud ks clusters. This value is required.
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example cluster ca get command 

ibmcloud oc cluster ca get --cluster my_cluster







 ibmcloud oc cluster ca rotate 

Virtual Private Cloud

Classic infrastructure

Rotate the certificate authority (CA) certificates of a cluster. Rotating invalidates certificates signed by the cluster's previous CA and issues certificates signed by the cluster's new CA to worker nodes.

Before you run this command, follow the steps in [Rotating CA certificates in your cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-securitycert-rotate) to ensure that any tooling that uses the old CA certificates is updated to use the new certificates and to update your worker nodes.

ibmcloud oc cluster ca rotate --cluster CLUSTER [-f] [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

-f
: Optional: Force the command to run with no user prompts.

-q
: Optional: Do not show the message of the day or update reminders.



 Example cluster ca rotate command 

ibmcloud oc cluster ca rotate --cluster my_cluster







 ibmcloud oc cluster ca status 

Virtual Private Cloud

Classic infrastructure

After you run [ibmcloud oc cluster ca rotate](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_ca_rotate), view the rotation status of certificate authority (CA) certificates for a cluster.

ibmcloud oc cluster ca status --cluster CLUSTER [-q]

Minimum required permissions
ibmcloud ks ingress domain secret rm --cluster CLUSTER --domain DOMAIN [-f] [--output OUTPUT] [-q]

Minimum required permissions
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster where the domain is applied.

--domain DOMAIN
: Required. The domain you want to remove the secret from.

-f

--output OUTPUT
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example ingress domain secret rm command 

ibmcloud ks ingress domain secret rm --cluster CLUSTER --domain DOMAIN [-f] [--output OUTPUT] [-q]







 ibmcloud ks ingress domain update 

Update an Ingress domain for a cluster to change the hostnames or IP addresses associated with the domain. This command updates all the resources in your cluster with the specified IP addresses or hostnames and changes your app URLs.

ibmcloud ks ingress domain update --cluster CLUSTER --domain DOMAIN [--hostname HOSTNAME] [--ip IP] [--ip IP] [-q]

Note that when you add IP addresses or hostnames, you must include any IPs or hostnames that are currently registered to the domain. The domain updates with the exact values specified, so any current IP addresses or hostnames are overwritten if they are not included. For example, if 52.137.182.166 is currently registered to your domain and you want to add 52.137.182.270, you must specify --ip 52.137.182.166 --ip 52.137.182.270 in the command.

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster where the domain is applied.

--domain DOMAIN
: Required. The domain you want to update.

--hostname HOSTNAME
ibmcloud ks ingress domain secret rm --cluster CLUSTER --domain DOMAIN [-f] [--output OUTPUT] [-q]

Minimum required permissions
: Operator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster where the domain is applied.

--domain DOMAIN
: Required. The domain you want to remove the secret from.

-f

--output OUTPUT
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.



 Example ingress domain secret rm command 

ibmcloud ks ingress domain secret rm --cluster CLUSTER --domain DOMAIN [-f] [--output OUTPUT] [-q]







 ibmcloud ks ingress domain update 

Update an Ingress domain for a cluster to change the hostnames or IP addresses associated with the domain. This command updates all the resources in your cluster with the specified IP addresses or hostnames and changes your app URLs.

ibmcloud ks ingress domain update --cluster CLUSTER --domain DOMAIN [--hostname HOSTNAME] [--ip IP] [-q]

Note that when you add IP addresses or hostnames, you must include any IPs or hostnames that are currently registered to the domain. The domain updates with the exact values specified, so any current IP addresses or hostnames are overwritten if they are not included. For example, if 52.137.182.166 is currently registered to your domain and you want to add 52.137.182.270, you must specify --ip 52.137.182.166, 52.137.182.270 in the command.

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster where the domain is applied.

--domain DOMAIN
: Required. The domain you want to update.

--hostname HOSTNAME
: For VPC clusters.
To prevent breaking changes, don't change the predefined view, edit, admin, and cluster-admin cluster roles. Custom RBAC roles are in addition to and don't change or override any RBAC roles that you might have assigned with IBM Cloud IAM service access roles.



* Namespace access: To allow a user, access group, or service account to access a resource within a specific namespace, choose one of the following combinations:



* Create a role, and apply it with a role binding. This option is useful for controlling access to a unique resource that exists only in one namespace, like an app deployment.
* Create a cluster role, and apply it with a role binding. This option is useful for controlling access to general resources in one namespace, like pods.



* Cluster-wide access: To allow a user or an access group to access cluster-wide resources or resources in all namespaces, create a cluster role, and apply it with a cluster role binding. This option is useful for controlling access to resources that are not scoped to namespaces, like worker nodes, or resources in all namespaces in your cluster, like pods in each namespace.
* [Log in to your account. If applicable, target the appropriate resource group. Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)
* Ensure you that have the [Manager IBM Cloud IAM service access role](https://cloud.ibm.com/docs/containers?topic=containers-usersadd_users) for all namespaces.
* To assign access to individual users or users in an access group, ensure that the user or group has been assigned at least one [IBM Cloud IAM platform access role](https://cloud.ibm.com/docs/containers?topic=containers-usersadd_users) at the IBM Cloud Kubernetes Service service level.



To create custom RBAC permissions,



1. Create the role or cluster role with the access that you want to assign.



1. Create a .yaml file to define the role or cluster role.

kind: Role
* Administrator platform access role and Manager service access role for the ibm-observe Kubernetes namespaces in IBM Cloud Kubernetes Service.
* Viewer platform access role for IBM Log Analysis



Command options:

--cluster CLUSTER
: The name or ID of the cluster for which you want to list existing Monitoring configurations. To retrieve your cluster name or ID, run ibmcloud oc clusters. This value is required.

--instance LOGGING_INSTANCE
: The ID or name of the IBM Cloud Monitoring service instance for which you want to show the monitoring configuration. To retrieve the name, run ibmcloud resource service-instances. This value is required.
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: The name or ID of the cluster. To view VPC clusters, run ibmcloud ks cluster ls --provider vpc-gen2.

--type PUBLIC|PRIVATE
: The type of ALB: public or private.

--zone ZONE
: The VPC zone to deploy the ALB to.

--version IMAGE_VERSION
: Optional: The version of the image that you want the ALB to run. To list available versions, run ibmcloud ks ingress alb versions. To specify a version other than the default, you must first disable automatic updates by running the ibmcloud ks ingress alb autoupdate disable command. If you omit this option, the ALB runs the default version of the Kubernetes Ingress image type.

-q
: Optional: Do not show the message of the day or update reminders.



 Example ingress alb create vpc-gen2 command 

ibmcloud ks ingress alb create vpc-gen2 --cluster mycluster --type public --zone us-south-1 --version 1.1.2_2507_iks







 ibmcloud ks ingress alb disable 

Virtual Private Cloud

Classic infrastructure

Disable an ALB in your cluster. The ALB and its pods still exist, but stop routing traffic to your apps.

The previous alias for this command, ibmcloud ks ingress alb configure, is deprecated.

ibmcloud ks ingress alb disable --alb ALB_ID --cluster CLUSTER [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--alb ALB_ID
: Required: The ID for an ALB. To view the IDs for the ALBs in a cluster, run ibmcloud ks ingress alb ls --cluster CLUSTER.

-c, --cluster CLUSTER
: The name or ID of the cluster.
* Administrator platform access role and Manager service access role for the ibm-observe Kubernetes namespaces in IBM Cloud Kubernetes Service.
* Viewer platform access role for IBM Log Analysis



Command options:

--cluster CLUSTER
: The name or ID of the cluster for which you want to list existing Log Analysis configurations. To retrieve your cluster name or ID, run ibmcloud oc clusters. This value is required.

--instance LOGGING_INSTANCE
: The ID or name of the IBM Log Analysis service instance for which you want to show the logging configuration. To retrieve the name, run ibmcloud resource service-instances. This value is required.







 Monitoring commands 



 ibmcloud ob monitoring agent discover 

Virtual Private Cloud

Classic infrastructure

Discover Monitoring agents that you manually installed in your cluster without using the Red Hat OpenShift on IBM Cloud observability plug-in, and make this monitoring configuration visible to the plug-in so that you can use the observability plug-in commands and functionality in the IBM Cloud console to manage this configuration.

ibmcloud ob monitoring agent discover --cluster CLUSTER [--instance MONITORING_INSTANCE]

Minimum required permissions:



* Administrator platform access role and Manager service access role for all Kubernetes namespaces in IBM Cloud Kubernetes Service
* Viewer platform access role for IBM Cloud Monitoring



Command options:

--cluster CLUSTER
: The name or ID of the cluster where you manually created a Monitoring configuration without using the Red Hat OpenShift on IBM Cloud observability plug-in. To retrieve your cluster name or ID, run ibmcloud oc clusters. This value is required.

--instance MONITORING_INSTANCE
: The ID or name of the IBM Cloud Monitoring service instance that you use in your monitoring configuration. This value is optional. If you don't provide this value, the IBM Cloud Monitoring service instance is automatically retrieved





 ibmcloud ob monitoring config create 

Virtual Private Cloud

Classic infrastructure

Create a monitoring configuration for your cluster to automatically collect cluster and pod metrics, and send them to IBM Cloud Monitoring.

This command deploys a Monitoring agent as a Kubernetes daemon set in your cluster.
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

--output json
: Optional: Prints the command output in JSON format.





 ibmcloud oc cluster addon options 

Virtual Private Cloud

Classic infrastructure

Before you enable an add-on, view its installation options.

ibmcloud oc cluster addon options --addon ADDON [--output OUTPUT] [-q] [--version VERSION]

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--addon ADDON
: Required: The name of the addon. To list available add-ons, run ibmcloud oc cluster addon versions.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.

--version VERSION
: Optional: Specify an add-on version to display options for. If no version is specified, the default version's options are displayed. To list available add-on versions, run ibmcloud oc cluster addon versions.





 ibmcloud oc cluster addon update 

Virtual Private Cloud

Classic infrastructure

Update an installed add-on.

ibmcloud oc cluster addon update --addon ADD-ON_NAME --cluster CLUSTER [-f] [-q] [--version VERSION] [-y]

Minimum required permissions
: None

Command options:

--addon ADD-ON_NAME
: Required: Specify an add-on name, such as istio, to update. To see installed add-ons, run ibmcloud oc cluster addon ls --cluster <cluster_name_or_ID>.

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

-f
: Optional: Force the command to run with no user prompts.

-q
ibmcloud oc ingress instance unregister --cluster CLUSTER --name NAME [-q]

Minimum required permissions
: Administrator platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--c, --cluster CLUSTER
: Required. The name or ID of the cluster.

--name
: Required. The name of the Secrets Manager instance to remove.

-q
: Optional: Do not show the message of the day or update reminders.

Example:

ibmcloud oc ingress instance unregister --cluster my-cluster --name my-secrets-manager-instance





 ibmcloud oc ingress lb get 

Virtual Private Cloud

Classic infrastructure

Get the configuration of load balancers that expose Ingress ALBs in your cluster.

For example, if you previously ran commands such as [ibmcloud oc ingress lb proxy-protocol enable](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_ingress_lb_proxy-protocol_enable), you can use this command to view your configuration changes.

ibmcloud oc ingress lb get --cluster CLUSTER [--output OUTPUT] [-q]

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

-f
: Optional: Force the command to run with no user prompts.

-q
: Optional: Do not show the message of the day or update reminders.



 Example ingress lb get command 

ibmcloud oc ingress lb get --cluster mycluster







 ibmcloud oc ingress lb proxy-protocol disable 

Virtual Private Cloud

Disable the NGINX PROXY protocol for the load balancers in front of all Ingress ALBs in your cluster so that client connection information is no longer passed in request headers to ALBs.
ibmcloud ob logging config create 

Virtual Private Cloud

Classic infrastructure

Create a logging configuration for your cluster to automatically collect pod logs and send them to IBM Log Analysis.

This command deploys a Log Analysis agent as a Kubernetes daemon set in your cluster. The agent collects logs with the extension .log and extensionless files that are stored in the /var/log directory of your pod from all projects, including kube-system. For more information, see [Forwarding cluster and app logs to IBM Log Analysis](https://cloud.ibm.com/docs/openshift?topic=openshift-healthopenshift_logging). For more information about IBM Log Analysis, see [Securing your data](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-mng-data).

ibmcloud ob logging config create --cluster CLUSTER --instance LOGGING_INSTANCE [--logdna-ingestion-key INGESTION_KEY] [--private-endpoint]

Minimum required permissions:



* Administrator platform access role and Manager service access role for all Kubernetes namespaces in IBM Cloud Kubernetes Service
* Editor platform access role and Manager server access role for IBM Log Analysis



Command options:

--cluster CLUSTER
: The name or ID of the cluster for which you want to create a logging configuration for IBM Log Analysis. To retrieve your cluster name or ID, run ibmcloud oc clusters. This value is required.

--instance LOGGING_INSTANCE
: The ID or name of the IBM Log Analysis service instance that you want to use to create the logging configuration. The service instance must be in the same IBM Cloud account as your cluster, but can be in a different resource group or region than your cluster. To create a service instance, follow the steps in [Provision an instance](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-provision). This value is required.

--logdna-ingestion-key INGESTION_KEY
: The Log Analysis ingestion key that you want to use for your configuration.
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

Command options:

--addon ADDON
: Required: The name of the addon. To list available add-ons, run ibmcloud ks cluster addon versions.

--output json
: Optional: Prints the command output in JSON format.

-q
: Optional: Do not show the message of the day or update reminders.

--version VERSION
: Optional: Specify an add-on version to display options for. If no version is specified, the default version's options are displayed. To list available add-on versions, run ibmcloud ks cluster addon versions.





 ibmcloud ks cluster addon update 

Virtual Private Cloud

Classic infrastructure

Update an installed add-on.

ibmcloud ks cluster addon update --addon ADD-ON_NAME --cluster CLUSTER [-f] [-q] [--version VERSION] [-y]

Minimum required permissions
: None

Command options:

--addon ADD-ON_NAME
: Required: Specify an add-on name, such as istio, to update. To see installed add-ons, run ibmcloud ks cluster addon ls --cluster <cluster_name_or_ID>.

-c, --cluster CLUSTER
: Required: The name or ID of the cluster.

-f
: Optional: Force the command to run with no user prompts.

-q
: Optional: Do not show the message of the day or update reminders.

--version VERSION
: Optional: Specify the version to update the add-on to. If no version is specified, the add-on is updated to the default version. To list available add-on versions, run ibmcloud ks cluster addon versions.





 ibmcloud ks cluster addon versions 

Virtual Private Cloud

Classic infrastructure

View a list of supported versions for managed add-ons in IBM Cloud Kubernetes Service.

ibmcloud ks cluster addon versions [--addon ADD-ON_NAME] [--output json] [-q]