Hi Jagdish,
I'm not sure why your pods aren't able to communicate with each other.
The network interfaces that ACS sets up are linked through a L2 virtual switch
and should be able to talk to each other directly.
Which networking service are you using?
https://kubernetes.io/docs/concepts/cluste
Charlie, I think you'll have to explain a bit more about your environment
to get an answer. what type of storage is it? Where did you migrate the VM
from and to? What types() of hypervisors are you using? Though saying *the*
agent logs suggests KVM, you are still leaving people guessing a lot.
On
Thanks Andrija. Yes that's the better way
On Thu, Jan 9, 2020 at 10:13 AM Andrija Panic
wrote:
> You can try editing the User role (ACS 4.9+) and explicitly add the deny
> "ACL" for those API calls which you want to deny
> Later just remove the "ACL" rules.
>
> On Thu, 9 Jan 2020 at 09:59, Rakes
Editing the roles is a great idea and proly the easiest, not to mention
if you disable the user all its VMs will be automatically shut down,
might be something you want to avoid.
---
Sent from the Delta quadrant using Borg technology!
On 2020-01-09 09:12, Andrija Panic wrote:
You can try editi
You can try editing the User role (ACS 4.9+) and explicitly add the deny
"ACL" for those API calls which you want to deny
Later just remove the "ACL" rules.
On Thu, 9 Jan 2020 at 09:59, Rakesh Venkatesh
wrote:
> Hello folks
>
>
> Is there a better way to disable all the VM related API's for a sh
Hello folks
Is there a better way to disable all the VM related API's for a short
duration of time? Like I want to disable stop/start/migrate/destroy VM API.
I'm thinking of disabling the user so that the user cant send any API
requests. After some time I will enable the user back. Is there any o
