Nginx Ingress is trying to use deleted load balancer

See also questions close to this topic

• Upload file from html when block public access is true

  I am using django-s3direct to file upload

  https://github.com/bradleyg/django-s3direct

  Using IAM role setting because I upload the file from the server on ECS container.

  Now I set the blockPublicAccess of S3 false.

  When uploading images from html, there comes error.

  https://s3.ap-northeast-1.amazonaws.com/static-resource-v/images/c64d6e593de44aa5b10dcf1766582547/_origin.jpg?uploads (403 (Forbidden)
  )
  
  initiate error: static-resource-v/line-assets/images/c64d6e593de44aa5b10dcf1766582547/_origin.jpg AWS Code: AccessDenied, Message:Access Deniedstatus:403
  

  OK, it is understandable.

  Browser try to access the for initiation.

  However there is any way to upload file from browser when blockPublicAccess is true??
• Linux on Lightsail instance is asking for a password and it's not working

  I'm trying to restart mariaDB on Ubuntu but it's not letting me.

  I enter:

  systemctl restart mariadb
  

  and get:

  ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-units ===
  
  Authentication is required to restart 'mariadb.service'.
  
  Authenticating as: Ubuntu (ubuntu)
  
  Password: 
  
  polkit-agent-helper-1: pam_authenticate failed: Authentication failure
  
  ==== AUTHENTICATION FAILED ===
  

  I have the same password for all functions so I do not understand why it is not working. What can I do?
• AWS Pinpoint sendMessages() Addresses param field error

  I'm having trouble replicating the format of the params object's Addresses format in a way where I can easily add to the object.

  If I use this as the params with destinationNumber[0] and destinationNumber[1] in the format of 1 + 9 digit number ie 13334535667 then it sends the message to both numbers no problem.

   const params = {
          ApplicationId: applicationId,
          MessageRequest: {
              Addresses: {
                  [destinationNumber[0]]: {
                      ChannelType: 'SMS'
                  },
                  [destinationNumber[1]]: {
                      ChannelType: 'SMS'
                  }
              },
              MessageConfiguration: {
                  SMSMessage: {
                      Body: message,
                      Keyword: registeredKeyword,
                      MessageType: messageType,
                      OriginationNumber: originationNumber
                  }
              }
          }
      };
  

  I'm trying to replicate this format for Addresses, but I'm getting Unexpected key '13334535667' found in params.MessageRequest.Addresses['0']. The format my console output shows for Addresses is

  [
    { '12345678910': { ChannelType: 'SMS' } },
    { '12345678911': { ChannelType: 'SMS' } }
  ]
  

  I'm using a map to call this

  function createPhoneMessagingObject(phoneNumber: string) {
      return {
          [phoneNumber]: {
              ChannelType: 'SMS'
          }
      };
  }
  

  I tried wrapping key in array like in phone object, but per the output, the brackets goes away so maybe there's an easier/more correct way of doing this. I appreciate any help!
• Java Spring Webflux on Kubernetes: always [or-http-epoll-1], [or-http-epoll-2], [or-http-epoll-3], [or-http-epoll-4] despite configured resource

  Small question regarding a Java 11 Spring Webflux 2.6.6+ web app, containerized and deployed using Kubernetes please.

  From the web app application logs, I am seeing things such as:

  INFO [service,1bcce5941c742568,22c0ab2133c63a77] 11 --- [or-http-epoll-2] a.b.c.SomeClass  : Some message from the reactive pipeline.
  INFO [service,67cb40974712b3f4,15285d01bce9dfd5] 11 --- [or-http-epoll-4] a.b.c.SomeClass  : Some message from the reactive pipeline.
  INFO [service,5011dc5e09de30b7,f58687695bda20f2] 11 --- [or-http-epoll-3] a.b.c.SomeClass  : Some message from the reactive pipeline.
  INFO [service,8046bdde07b13261,5c30a56a4a603f4d] 11 --- [or-http-epoll-1] a.b.c.SomeClass  : Some message from the reactive pipeline.
  

  And always, I can only see [or-http-epoll-1] [or-http-epoll-2] [or-http-epoll-3] [or-http-epoll-4] which I think stands for: [reactor-http-epoll-N]

  The problem is, no matter how much CPU I allocate from Kubernetes, it is always those 4, no less, no more.

  I tried:

    resources:
              requests:
                cpu: 1
                memory: 1G
              limits:
                cpu: 2
                memory: 2G
  
    resources:
              requests:
                cpu: 4
                memory: 4G
              limits:
                cpu: 6
                memory: 6G
  
    resources:
              requests:
                cpu: 10
                memory: 10G
              limits:
                cpu: 10
                memory: 10G
  
  

  But again, always only those 4.

  I am having a hard time understanding what is the problem here, and why am I stuck with only/always 4 "or-http-epoll-".

  Thank you
• How does Kubernetes and Terraform work seamlessly together and what role do they each undertake?

  I am a bit confused about the individual roles of Kubernetes and Terraform when using them both on a project.

  Until very recently, I had a very clear understanding of both their purposes and everything made sense to me. But, then I heard in one of Nana's videos on Terraform, that Terraform was also very advanced in orchestration and I got confused.

  Here's my current understanding of both these tools:

  • Kubernetes: Orchestration software that controls many docker containers working together seamlessly. Kubernetes makes sure that new containers are deployed based on the desired infrastructure defined in configuration files (written with the help of a tool like Terraform, as IaC).

  • Terraform: Tool for provisioning, configuring, and managing infrastructure as IaC.

  So, when we say that Terraform is a good tool for orchestration, do we mean that it's a good tool for orchestrating infrastructure states or docker containers as well?

  I hope someone can clear that out for me!
• Update node condition type in status

  I am trying to patch, clear Node conditions in OpenShift and/or Kubernetes cluster on a worker node. Patch isn't working, trying even workarounds, maybe update the key in etcd.

  Main problem that i created new node conditions and then i removed them but they are not removed from list although they are no longer there or being updated by the controller.

  $ oc describe node node1.example.com
  
  Conditions:                 
    Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
    ----             ------  -----------------                 ------------------                ------                       -------
    ExampleToRemove        False   Wed, 13 Feb 2019 15:09:42 -0500   Wed, 13 Feb 2019 11:05:57 -0500   KubeletHasSufficientDisk     kubelet has sufficient disk space available
    MemoryPressure   False   Wed, 13 Feb 2019 15:09:42 -0500   Wed, 13 Feb 2019 11:05:57 -0500   KubeletHasSufficientMemory   kubelet has sufficient memory available
    DiskPressure     False   Wed, 13 Feb 2019 15:09:42 -0500   Wed, 13 Feb 2019 11:05:57 -0500   KubeletHasNoDiskPressure     kubelet has no disk pressure
    PIDPressure      False   Wed, 13 Feb 2019 15:09:42 -0500   Wed, 13 Feb 2019 11:05:57 -0500   KubeletHasSufficientPID      kubelet has sufficient PID available
    Ready            True    Wed, 13 Feb 2019 15:09:42 -0500
  
• setting up Application load balancer with Global accelerator with Nginx target group upstream to IIS

  I have set up an application Load balancer with Global accelerator and Nginx Proxy pass to different IIS upstream based upon hostname. The website works well and can access the websites globally. some times customers had issues accessing websites with 500 error codes. we have an error logger configured with our app we can see double IP addresses in ROMOTE_ADDR for some of the request

  For requests with double ip addresses, it throws a 500 Internal server error. and other request with single IP address are good

  nginx.conf

  proxy_set_header        Host $host;
    proxy_set_header        Connection "";
    proxy_set_header        X-Real-IP $http_x_forwarded_for;
    proxy_set_header        remote_addr $http_x_forwarded_for;
    proxy_set_header        X-Forwarded-For $http_x_forwarded_for;
    proxy_hide_header        Server;
    proxy_hide_header        X-Powered-By;
    proxy_hide_header        X-AspNet-Version;
    proxy_headers_hash_bucket_size 64;
  
    real_ip_header   X-Forwarded-For;
    set_real_ip_from 10.15.0.0/16;
    real_ip_recursive on;
  
  enter code here
  

  virtual host

  proxy_pass            http://www-servers;
      proxy_read_timeout    90;
      proxy_connect_timeout 90;
      proxy_http_version    1.1;
      proxy_set_header      Host $host;
      proxy_set_header      Connection "";
      proxy_set_header      X-Real-IP $http_x_forwarded_for;
      proxy_set_header      remote_addr $http_x_forwarded_for;
      proxy_set_header      X-Forwarded-For $http_x_forwarded_for;
      proxy_hide_header      Server;
      proxy_hide_header      X-Powered-By;
      proxy_hide_header      X-AspNet-Version;
  
  
  
  
  
  double ip address   -  Double IP Address: 72.194.29.174, 104.129.198.101
  

  sometimes there are three IP addresses

  Double IP Address: 73.223.72.109, 172.18.0.3, 64.62.158.119
  

  what header we can set to get the correct IP address and prevent some connection to log double ip's
• service.beta.kubernetes.io/aws-load-balancer-private-ipv4-addresses nlb for ingress controller on eks not creating

  I have deployed nginx ingress controller with helm whit this annotation

  annotations: service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled: 'true' service.beta.kubernetes.io/aws-load-balancer-type: nlb-ip service.beta.kubernetes.io/aws-load-balancer-subnets: "subnet-0d0d77bf83700c49f, subnet-065709c94de30e151" service.beta.kubernetes.io/aws-load-balancer-private-ipv4-addresses: 10.0.0.185, 10.0.0.211 service.beta.kubernetes.io/aws-load-balancer-internal: "true"

  But the NLB result of run not don't take the ip that I indicate in the file
• nginx ingress on kuberentes sees node ip address instead of the public internet resource requestor

  I have a kubernetes cluster and a nginx ingress. I have deployed an ingress to route traffic from a domain example.org to a specific container. Now, I am trying to block all requests which are not coming from a whitelisted ip range. Therefore I annotated the created ingress with nginx.ingress.kubernetes.io/whitelist-source-range. However, all traffic gets blocked so I looked at the logs from nginx and I realized that actually nginx sees the internal node ip address instead of the requestors public internet address.

  2022/05/06 11:39:26 [error] 10719#10719: *44013470 access forbidden by rule, client: 172.5.5.84, server: example.org, request: "GET /.svn/wc.db HTTP/1.1", host: "example.org"
  

  I am not sure what is actually wrong. When I remove the whitelist annotation, then everything works as expected.