Re: Autoscaling groups

[Clayton Coleman]

It is not possible to do to masters.  You'd need to create a new cluster.

I don't think the node group addition in in official docs yet because it's
still tech preview.  So Ansible is the best you'll get for now.

On Tue, Jul 24, 2018 at 10:04 AM David Conde  wrote:

> Thanks,
>
> Is it possible to also do that with masters post upgrade? Do you have any
> info you could point me at to create the new node groups post upgrade?
>
>
>
> On Tue, Jul 24, 2018 at 3:00 PM Clayton Coleman 
> wrote:
>
>> Upgrading from regular nodes to autoscaling groups is not implemented.
>> You’d have to add new node groups post upgrade and manage it that way.
>>
>> > On Jul 24, 2018, at 7:22 AM, David Conde  wrote:
>> >
>> > I'm in the process of upgrading an origin cluster running on AWS from
>> 3.7 to 3.9 using openshift ansible. I'd like the new instances to be
>> registered in autoscaling groups.
>> >
>> > I have seen that if I create a new origin 3.9 cluster using the AWS
>> playbooks this happens as part of the install, how would I go about
>> ensuring this happens as part of the upgrade from 3.7 to 3.9?
>> >
>> > Thanks,
>> > Dave
>> > ___
>> > users mailing list
>> > users@lists.openshift.redhat.com
>> > http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>
>
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

enabling unsafe sysctls in OSO

[Peter Heitman]

I need to set some sysctls in a couple of my DeploymentConfigs for their
pods. I have followed
https://docs.openshift.com/container-platform/3.9/admin_guide/sysctls.html but
when I deploy the pods and exec in to the container, the sysctls are not
set. My dc file contains:

objects:
- kind: DeploymentConfig
  apiVersion: v1
  metadata:
name: cl
annotations:
  security.alpha.kubernetes.io/sysctls:
net.ipv4.ip_local_port_range=9000 65500
  security.alpha.kubernetes.io/unsafe-sysctls:
net.core.rmem_default=4194304,net.core.rmem_max=16777216,net.core.wmem_default=262144,net.core.wmem_max=16777216,net.ipv4.tcp_rmem=4096
87380 16777216,net.ipv4.tcp_wmem=4096 65536 16777216
  spec:

and I have updated the node-config.yaml file with

kubeletArguments:
  node-labels:
  - role=app
  experimental-allowed-unsafe-sysctls:
  - "net.core.*,net.ipv4.tcp_rmem,net.ipv4.tcp_wmem"

On the minions I have the same values set for those sysctls at the host
level.

Any ideas on why this is successfully creating the pods but not setting the
sysctls? Has anyone gotten this to work?

Peter
___
users mailing list
users@lists.openshift.redhat.com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users