- Community Home
- >
- Software
- >
- HPE Morpheus Software
- >
- HPE Morpheus Enterprise
- >
- Morpheus add external Kubernetes Cluster
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-08-2023 08:50 PM
08-08-2023 08:50 PM
Morpheus add external Kubernetes Cluster
Hello Expert,
I tried to add an external Kubernetes cluster to Morpheus, it’s created by using Rancher, but I found strange things and don’t have any idea how it happened, I deploy pod/deployment by using “Spec Template”, but the deployment is deployed to Rancher K3s local-node…
-
Add rancher-cluster to Morpheus
-
deploy a Spec Template and respond it is unchanged and service is failed
-
deployment didn’t show up in this cluster
-
The deployment and morpheus-agent is deployed in rancher local-node, and the morpheus-agent image seems can’t pull?
- Tags:
- K8s
- Kubernetes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2023 07:20 AM
11-30-2023 07:20 AM
Re: Morpheus add external Kubernetes Cluster
Sorry just catching up on this. Unsure if you resolved, but currently the kubectl commands from Morpheus utilize the K8s api connection. So Morpheus must be able to resolve and connect (typically via port 6443) to the cluster. [agent comms coming very soon]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2024 08:08 AM
01-11-2024 08:08 AM
Re: Morpheus add external Kubernetes Cluster
Hi @WillyChen,
I’m trying to import Rancher Cluster into Morpheus but I don’t know where to collect API Token as the requirement. I tried to put ‘secret key’ from a Rancher Access Key into the API Token box but it did not work. Can you please leave an instruction? Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2024 08:27 AM
01-11-2024 08:27 AM
Re: Morpheus add external Kubernetes Cluster
I believe you can pull it from the UI in Rancher, but this post of creating a service account references pulling the API key and may be useful:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-11-2024 08:56 AM
01-11-2024 08:56 AM
Re: Morpheus add external Kubernetes Cluster
Hi @cbunge ,
Thank you for your reply, I followed the instruction you provided (as the same website document), and it seems I’m still in the error. Although I created a service account named ‘morpheus’ before I ran the command to Gather Service Account Token, it still returns ‘No resources found in morpheus namespace.’
I also try to pull Secret Key shown in the image for API Token requirement box but it does not work. Thank you again @cbunge !