search

k2v-academy / K2View-Academy

Other
0 stars 0 forks source link

Fabric Console on Cloud Native Deployment #1051

Closed F78aPg0zjWnRKWkYrBd6lShvmAYl8doniMtEnFN closed 4 months ago

F78aPg0zjWnRKWkYrBd6lShvmAYl8doniMtEnFN commented 4 months ago

Fabric+Studio 7.2.2 image through a Space from k2cloud

How to open one or more terminal sessions to Fabric console when Fabric is deployed on K8S?

Note: I know that it can be accessed through the Fabric Portal, but that's not what I want.

I logged into the Fabric pod with:

I tried to run fabric, but it is not in the path.

I cd ~/workspace/fabric/bin and run it from there as ./fabric, but it complains with

I assume that this error is because no user credentials were passed and, as such, it is trying admin.

Anyway, I tried ./fabric -u admin -p admin and got the same error.

Considering that login was done through k2cloud login, how to define user and password for login? I assume that user should be the email I used to login into k2cloud, but would the password be a SAML token? If so, how to capture it?

Please advise. Thanks.

157aq9Ud3GJlkIVikTS1SzhhiP3x1Vrj0jAjZ3X commented 4 months ago

Access via kubectl shall not be done, unless for maintenance.

F78aPg0zjWnRKWkYrBd6lShvmAYl8doniMtEnFN commented 4 months ago

Access via kubectl shall not be done, unless for maintenance.

It is reasonable assumption on production environments, although not always practical for support considering that some projects disable Web Admin and others doesn't allow Studio.

But for development and testing, is it only the terminal in Studio or the terminal in Admin the option? Both cases don't allow multiple terminal sessions.

So, in a scenario of maintenance, how to handle the error I initially described?

BTW, I tried to create admin user through Web Admin and also through Fabric console and it doesn't let due to some exception when integrating with Cassandra.

ERROR: You have to be logged in and not anonymous to perform this request

image Is this expected?

Please advise. Thanks.

157aq9Ud3GJlkIVikTS1SzhhiP3x1Vrj0jAjZ3X commented 4 months ago

you can open multiple fabric terminal sessions (you did not explain what is needed for), by opening several browser tabs. please do not use the kubectl for functionality. This is not the right way users shall use. In addition, most users do not have such access at all:

not at SaaS not at self host at cloud * on prem as K8s in a box is usually installed on VM, not on personal machines.

From: Fábio Corrêa @.> Sent: Wednesday, April 24, 2024 10:54 PM To: k2view-academy/K2View-Academy @.> Cc: Eyal Orbach @.>; Assign @.> Subject: Re: [k2view-academy/K2View-Academy] Fabric Console on Cloud Native Deployment (Issue #1051)

Access via kubectl shall not be done, unless for maintenance.

It is reasonable assumption on production environments, although not always practical for support considering that some projects disable Web Admin and others doesn't allow Studio.

But for development and testing, is it only the terminal in Studio or the terminal in Admin the option? Both cases don't allow multiple terminal sessions.

So, in a scenario of maintenance, how to handle the error I initially described? Thanks.

— Reply to this email directly, view it on GitHubhttps://github.com/k2view-academy/K2View-Academy/issues/1051#issuecomment-2075730106, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARWMWJDMP7ZAIHBMLT5FOLDY7AEXJAVCNFSM6AAAAABGWXDIXKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZVG4ZTAMJQGY. You are receiving this because you were assigned.