Skip to main content

Log - Sprint 2 🛫

· 2 min read

Date​

Flight Logs contain information relating to steps completed between 05/09 - 05/12

Key Accomplishments​

  • Worked with engineering to fix the resource issues with the original operator build and successfully deployed operator with correct resources sizes.
  • Successfully applied CR to point to the correct repo for navigator image after patching daemonset.
  • Successfully got the Ingress to work and connect to the host through the browser on a secure connection.

Challenges​

  • This customer environment requires the resource restrictions set into any container spun up. The temporary job pod which uses the operator limit does not contain any mechanism to set these restrictions.
  • The customer was having issues accessing the newly made Operator image, due to registry access permissions. We had to push image to a public registry with the tag trv2202 for the customer to pull and then have them push it to their own private registry.
  • We had issues bringing the Filenet pods online after successfully getting the new Operator image in the client environment.
  • Folder-prepare-container kept erroring out due to us implementing a readOnlyRootFilesystem and prevented Dynatrace.
  • We had issues connecting to the host through the browser when trying to get the Ingress to work. We thought this was due to the host name being in the wrong location in the YAML file, but it was actually due to the route 53 external DNS operator taking some time to pick everything up.

Lessons Learned​

  • Operator deployment takes care of requesting resources for new containers. Operator deployment creates an initialization container that spins up and it does not have the ability to set up CPU and memory limits. In the future, managing resources in environment can take care of this issue.
  • When applying the Ingress, give the route 53 DNS operator time to pick up the correct host name before trying to access it through the browser.
  • When accessing the host, we need to create a certificate to give it a secure connection. This will prevent any "insecure connection" connection loops.

Action Items​

  • Followup with engineering to allow RW root fs to allow Dynatrace to work

Up Next​

  • Use the Operator to bootstrap the gcd domain and object store and then create a navigator desktop using the CR file.