user want to delete all permissions and keep only modify permission for everyone and full permission to system. Like this.
But present with icacls command
icacls "%ProgramData%\myfolder\Licensing" /grant Everyone:M SYSTEM:F
how to remove all other entries and keep only this.
whether icacls or any other command line
I tried
icacls "%ProgramData%\myfolder\Licensing" /grant Everyone:M SYSTEM:F /inheritance:r
But it is not setting like that.
I have a gitlab runner configured in the aws ec2 instance.
For any aws deployments, we simply added the role to the ec2 instance.
But, our gitlab runner is configured in one aws account. And we need to apply aws terraform templates on a different account(not IAM, complete different root account).
How to give gitlab runner permission to this different aws account
We have one cluster in aks. Where we deployed consul helm chart in consul namespace. It created many CRDs.
The using these CRDs internally created one more namespace applicationns
When we deleted consul, it deleted.
Then, when we trying to delete applicationns, it stuck in terminating state for a long time.
So, followed this link and deleted the namespace.
Now, when I ran "kubectl get ns", it is not showing but.
kubectl get serviceintentions -n applicationns
NAME SYNCED LAST SYNCED AGE
servi1 True 41d 42d
servi2 True 41d 42d
servi3 True 41d 42d
Please suggest how to cleanup, there are many CRDs like them. Not deleting also.
I have grafana and jenkins running on same azure vm. For jenkins: http://localhost:8080 For grafana: http://localhost:3000
I thought to set nginx in such a way. customdomain.com/grafana should go to http://localhost:3000 customdomain.com/jenkins or customdomain.com should go to http://localhost:8080
But even /grafana is going to jenkins only.
How to fix that?
The, default config file for mapping in nginx.
location /grafana {
include /etc/nginx/proxy_params;
proxy_pass http://localhost:3000;
proxy_read_timeout 60s;
# Fix the "It appears that your reverse proxy set up is broken" error.
# Make sure the domain name is correct
#proxy_redirect http://localhost:3000 https://customdomain.com;
}
location / {
include /etc/nginx/proxy_params;
proxy_pass http://localhost:8080;
proxy_read_timeout 60s;
# Fix the "It appears that your reverse proxy set up is broken" error.
# Make sure the domain name is correct
proxy_redirect http://localhost:8080 https://customdomain.com;
}
I have installed nginx along with jenkins on ubuntu 21 machine.
Configured nginx to redirect 80 traffic to 8080 using the steps in this link
Now, able to redirect the traffic from 80 to 8080. So, to disable direct access to jenkins from 8080 externally. Changed the arguments in /etc/default/jenkins to add line --httpListenAddress=127.0.0.1
Now, the jenkins arguments line is as below.
JENKINS_ARGS="--webroot=/var/cache/$NAME/war --httpPort=$HTTP_PORT --httpListenAddress=127.0.0.1"
Then, restarted the machine also after that but still able to access directly with 8080 port.
Please suggest how to achieve this.
azureuser@jenkins:~$ ss -lnpt
State Recv-Q Send-Q Local Address:Port Peer Address:Port Process
LISTEN 0 511 0.0.0.0:80 0.0.0.0:*
LISTEN 0 4096 127.0.0.53%lo:53 0.0.0.0:*
LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
LISTEN 0 4096 *:3000 *:*
LISTEN 0 50 *:8080 *:*
LISTEN 0 128 [::]:22 [::]:*
azureuser@jenkins:~$ ps auxw | grep jenkins
jenkins 6761 0.1 11.8 3036280 416756 ? Ssl Mar29 8:08 /usr/bin/java -Djava.awt.headless=true -jar /usr/share/java/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080
azureus+ 86025 0.0 0.0 8548 2356 pts/0 S+ 19:09 0:00 grep --color=auto jenkins
I am using windows 10 professional edition. Installed virtualbox and also enable virtualization on bios, that's why able to run windows 10 64bit machines as VMs in virtualbox.
When I started minikube, with below command, getting error as virtualization not enabled.
C:\WINDOWS\system32>minikube start --vm-driver=virtualbox
* minikube v1.19.0 on Microsoft Windows 10 Enterprise 10.0.19044 Build 19044
* Using the virtualbox driver based on existing profile
* Starting control plane node minikube in cluster minikube
* Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
! StartHost failed, but will try again: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
* Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
* Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
X Exiting due to HOST_VIRT_UNAVAILABLE: Failed to start host: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
* Suggestion: Virtualization support is disabled on your computer. If you are running minikube within a VM, try '--driver=docker'. Otherwise, consult your systems BIOS manual for how to enable virtualization.
* Related issues:
- https://github.com/kubernetes/minikube/issues/3900
- https://github.com/kubernetes/minikube/issues/4730
How to fix this?
I already enabled in bios as in below screenshot.
Same with --driver also
minikube start --driver=virtualbox
* minikube v1.19.0 on Microsoft Windows 10 Enterprise 10.0.19044 Build 19044
* Using the virtualbox driver based on existing profile
* Starting control plane node minikube in cluster minikube
* Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
! StartHost failed, but will try again: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
* Creating virtualbox VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
* Failed to start virtualbox VM. Running "minikube delete" may fix it: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
X Exiting due to HOST_VIRT_UNAVAILABLE: Failed to start host: creating host: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
* Suggestion: Virtualization support is disabled on your computer. If you are running minikube within a VM, try '--driver=docker'. Otherwise, consult your systems BIOS manual for how to enable virtualization.
* Related issues:
- https://github.com/kubernetes/minikube/issues/3900
- https://github.com/kubernetes/minikube/issues/4730
I am trying to integrate azure kubernetes container insights with grafana dashboard.
The plugin for that
For that, I have installed grafana on an azure cloud ubuntu 20 machine following the steps in this link
Allowed 3000 port in azure network security rules and able to access grafana portal using public ip of the VM with 3000 port.
Logged in with admin and password also admin and changed it later after login. Found the details in getting started guide
Installed azure monitor plugin with below command on the ubuntu machine and restarted the server and able to see the plugin there.
grafana-cli plugins install grafana-azure-monitor-datasource
By following the steps in link, I am able to register a new application and create a secret to it in azure and used that service principal and provided permissions(contributor role) to the default workspace of container insights linked to azure kubernetes cluster, which I want to monitor.
Then, when I provided those details in the grafana azure monitor data source.But the details configuration page is different when compared to the one in link.
But still clicked on save and test and got message.
Above screen is different from 7,8 steps in this link
I tried to import dashboard 10956 as in step 10 on above link and got below error there.
Please suggest how to fix this
We can send email noification whether success or failure in email of jenkins pipeline.
But it is not visual to understand clearly by the team members.
So, I kept stage name in an environment variable and kept in the email subject where exactly it got failed.
But, it is would be more helpful if I can send the stage view which we can see in jenkins job page.
Like below.
Please suggest how to implement the same.
I am trying to access keyvault data from aks cluster.
By following this link
The system managed identity section below link is showing for vm scale set instead of aks. So I am trying with user managed identity section.
az aks show -g devtest-large -n devtest-large-cluster --query addonProfiles.azureKeyvaultSecretsProvider.identity.clientId -o tsv
gave me output as below value
9d0d9e08-a9f2-4085-a9d2-d61ae7624943
So for below command template
# set policy to access keys in your key vault
az keyvault set-policy -n <keyvault-name> --key-permissions get --spn <identity-client-id>
Below is the value I passed, but I am getting error there.
az keyvault set-policy -n devtest-large-keyvault --key-permissions get --spn d0d9e08-a9f2-4085-a9d2-d61ae7624943
Unable to find user with spn 'd0d9e08-a9f2-4085-a9d2-d61ae7624943'
Unable to get object id from principal name.
We have a properties file where all our application configuration is there, in key-value pairs.
All the key-value pairs is in single config.properties file.
So, I kept that data in configmap and linked to this file in kubernetes.
Working fine so far.
But, to increase security, we want to keep some key-value pairs as secrets.
But, how to refer those secrets in the config.properties file without changing any application logic.
Please suggest.
I have used github duplicate option with --bare in clone and uploaded to a different account in github.com
Used as in this link
Just as a process to handover the project to another team.
But there are recent changes in the original repository, how to sync those changes there, all branches.
In this page also, it was shown to create a separate vm in the same vnet to connect to postgres setup in a private vnet option selected.
Is there anyway to connect using azure bastion.please show the steps.
I have seen active choice parameter plugin from this link
Here, they have provided sample so that when I select a parameter, it should change the values of other parameter.
Like in Active Choices Reactive Parameter: Configuration Options (Example 02)
But, with me it is not working.
I have created an aks cluster and deployed an application there and exposed it as a service.
Can be accessible through LoadBalancer.
To access it internally, I created a windows VM in the same vnet (different subnet) of aks cluster and tried to access the application using cluster IP, but can't access it.
Any suggestions?
Because I got the similar issue with application gateway also, so tried this VM now but same issue.
