We are using https://github.com/poseidon/typhoon for our kubernetes cluster setup.
I want to set up a dashboard for kubernetes similar to https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/
I followed https://docs.aws.amazon.com/eks/latest/userguide/dashboard-tutorial.html and I am able to get the dashboard on my localhost
The issue with this is that "EVERY USER HAS TO FOLLOW THE SAME TO ACCESS THE DASHBOARD"
I was wondering if there was some way wherein we can access the dashboard via DomainName and everyone should be able to access it without much pre-set up required.
In dashboard documentation you can read:
Using Skip option will make Dashboard use privileges of Service
Account used by Dashboard. Skip button is disabled by default since
1.10.1. Use --enable-skip-login dashboard flag to display it.
So you can add --enable-skip-login to the dashboard to display skip button.
If your users don't want to login, they can click Skip button during login and use privileges of Dashboard service account.
Related
I am trying to login to Rundeck community (4.5.0) that I installed on a AWS ECS cluster behind an Application Load Balancer. The health checks on target groups are good/healthy and I can reach the landing page of Rundeck too.
Once I enter default admin credentials, the page keeps loading for more an hour and times out eventually. There are no error logs in Cloudwatch as well. Same image works locally but not on AWS setup.
Any ideas or suggestions on how to solve this is welcome.
You need to set RUNDECK_SERVER_FORWARDED=true env var in your deployment. Take a look at this.
Is there a way to set a dashboard in Grafana as the home without admin login ? I have a Helm chart that I deploy Grafana with so I would like to do this at a configuration level.
I could not see any options under http://docs.grafana.org/installation/configuration/ for grafana.ini
I'm able to do this manually by login as the admin for the default organization, starring a dashboard and setting that dashboard as the home under preferences. But ofcourse automating this through configuration would be ideal.
Not sure how to do it via .ini file. But you could make use of the Grafana API to get this done.
If you can figure out the Id of the dashboard.Or create via the API itself
Use /api/user/stars/dashboard/{id} to star the dashboard
Then update preference to set the dashboard as home.
Hope this helps.
I have a few websites running in Azure and bitbucket repositories are connected to the test-slots. I'm trying to give the developer access to the Deployment Options (and Log) using the Azure portal without him being able to do anything destructive to the Web Application itself.
I've found an article describing how to create custom roles, but whatever I try, I cannot give the developer readonly access to the Web App and still allow him to access the Deployment Options: both the Deployment Options and Continous Delivery (Preview) are greyed out.
What I've done is create a new role based on the existing "Website Contributor" role (because that one does show the Web App's Deplyment Options) and changed the microsoft.web/sites/* to read-permissions:
Microsoft.Authorization/*/read
Microsoft.Insights/alertRules/*
Microsoft.Insights/components/*
Microsoft.ResourceHealth/availabilityStatuses/read
Microsoft.Resources/deployments/*
Microsoft.Resources/subscriptions/resourceGroups/read
Microsoft.Support/*
Microsoft.Web/certificates/*
Microsoft.Web/listSitesAssignedToHostName/read
Microsoft.Web/serverFarms/read
Microsoft.Web/sites/read
Microsoft.Web/sites/*/read
Microsoft.Web/sites/slots/read
Microsoft.Web/sites/slots/*/read
However, it only works when I replace the last 4 lines with this
Microsoft.Web/sites/*
But here lies the problem: I do not want give the developer full access to the Web Apps. The thing that drives me crazy is that even if I query all actions for this resource provider using powershell
Get-AzureRMProviderOperation "Microsoft.Web/sites/*" | FT OperationName, Operation , Description -AutoSize
And if I add all these individually instead of Microsoft.Web/sites/*, then it still doesn't show the deployment options and continous delivery.
Does anyone know why I need to give full access to the sites or how I can add readonly access to the site and still get access to the deployment options?
Numerous forum posts and documentations specify extracting login info for the Kubernetes install from ~/.kube/config.
The problem I found: mine doesn't have a proper user account, it specifies a name and a token.
How do I get the account name so I can use the kubernetes-cockpit UI? Surprisingly there appears to be nothing on that topic - what to do if the config doesn't contain an account.
It depends on how you use Cockpit.
According to cockpit official page:
Used in a standard cockpit session:
If a user is able to use kubectl successfully when at their shell terminal, then that same user will able to use Kubernetes dashboard when logged into Cockpit
I suppose this is your scenario, so if you didn't change default settings, the cockpit will look for .kube/config itself, i.e. you should be able to login without specifying your account.
I have a Bluemix user and he has manager access to his space. He wants to create a custom dashboard in Access Trail Service in Bluemix console. However, he cannot see the default dashboard that comes out of the box with the creation of an Access Trail service instance. Is there any way to get the default dashboard to display?
To recreate the default Access Trail dashboard, open the Access Trail dashboard for your space in Bluemix where you have the problem and click Create a dashboard. The default dashboard for that space will be recreated.