You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Flight Logs contain information relating to steps completed between 02/13/24 - 02/15/24
10
+
11
+
## Key Accomplishments
12
+
- Client provisioned a small EKS cluster and was able to go through staging steps.
13
+
- Customer was able to do the workaround provided yesterday to support hierarchical image naming convention in Amazon ECR.
14
+
- Deployed OpenLDAP & Postgresql.
15
+
- Successfully deployed the FileNet Operator into the customer's AWS EKS environment by manual process.
16
+
17
+
## Challenges
18
+
-**Postgresql Failure:** Permission issue while deploying postgresql.
19
+
-**Error Message:** "chmod: changing permission of '/var/lib/postgresql': Operation not permitted"
20
+
-**Solution:** Client used “efs-sc” (file storage) from the the FNCM Operator CR yaml. The postgres-pvc.yaml said to use “ebs-gp3-sc” (block storage). Switched the storageclass to fix the error.
21
+
22
+
-**Amazon ECR:** ECR has a flat structure so to maintain hierarchical naming structure of Filenet images client has to create separate repositories within ECR.
23
+
24
+
## Lessons Learned
25
+
- Make a note in the documentation to make it clear to use EBS(Block storage) instead of EFS for Postgresql.
26
+
- Amazon ECR behavior and workaround needs updated in the documentation.
27
+
- Both load balancer and nginx are needed. Nginx only works on ports 80 and 443 and other port goes through the load balancer.
28
+
29
+
## Action Items
30
+
31
+
## Next Steps
32
+
- Go through the FNCM CRD and fill out the configuration.
Flight Logs contain information relating to steps completed between 02/20/24 - 02/22/24
10
+
11
+
## Key Accomplishments
12
+
- Client scripted certain steps which should help if EKS cluster has to be reprovisioned and we need to redo the installation.
13
+
14
+
## Challenges
15
+
-**EKS Cluster clean up :** Client environment has a clean up process that deletes EKS cluster to save cost. Some of the resources in EKS failed to delete during this process. Client had to spend most of the week to create a new cluster and run through what we did the previous week.
16
+
17
+
## Lessons Learned
18
+
- Try to script/automate most of the steps to speed up the process if we run into issues like cluster deletion
19
+
- Database connection over SSL in CRD is disabled since we follow a MVP mode. In a production deployment client can set it up for more security.
20
+
21
+
## Action Items
22
+
- Client wants to know how to move their environment specific data into the extracted case package in an upgrade scenario.
23
+
- Any best practices and guidelines we can recommend on moving secrets to aws, etc in a production setting for security purposes.
24
+
- Research egress part in CR. For the time being we kept that section but set the sc_restricted_internet_access: false
25
+
- Documented differences in CR in the new case file.
26
+
27
+
## Next Steps
28
+
- Go through the FNCM CRD and fill out the configuration.
Flight Logs contain information relating to steps completed between 02/27/24 - 02/29/24
10
+
11
+
## Work In Progress
12
+
- Configure CR and resolve issues that we encounter while applying the yaml.
13
+
14
+
## Challenges
15
+
-**DBA Keytool:** We were getting image pull back error for “dba-keytool-initcontainer:23.0.2” while applying the CRD and pods are in crash back loop.
16
+
17
+
## Action Items
18
+
- Provided a solution for the client for DBA Keytool image issue. Update the CRD file with the block provided in the comment section of this PR - https://github.com/ibm-client-engineering/solution-filenet-aws/pull/96
19
+
- Track the case and provide any support as client is testing the solution before next weeks sessions.
20
+
21
+
## Next Steps
22
+
- Client to test the solution for DBA Keytool image issue.
23
+
- Go through the FNCM CRD and fill out the configuration.
Flight Logs contain information relating to steps completed between 03/05/24 - 03/07/24
10
+
11
+
## Key Accomplishments
12
+
- Client was able to apply FNCM CR. Pods came up without errors and they were able to access ACCE UI.
13
+
14
+
## Work In Progress
15
+
- IER deployment failed. New case has been opened to look into the issue before next weeks session.
16
+
17
+
## Challenges
18
+
-**EKS Cluster clean up :** Client environment has a clean up process that deletes EKS cluster to save cost. This process ran again and client has to provision cluster again. EKS cluster was deleted as part of their monthly clean up cycle.
19
+
20
+
-**IER Image:** Client is getting Back off error message for IER pod.
21
+
22
+
## Action Items
23
+
- Track the case TS015679454 and resolve the issue before next weeks sessions.
0 commit comments